All Articles

Meteor acceptance testing

Acceptance tests tests the features of your app. Those features are tested it the same way as users would use those features. We want to automate (as oppose to manual testing) this process. So test will start browser, which interact with your app’s UI in the same way as any user.

Sounds simple enough, right? But when you writing your tests, you can create technology debt even without knowing it. Before you start reading or after you finish, consider reading Testing Success Factors from - masters of testing.

We will need some software tools. I will list those here, then I will dive into installation / usage details down below.

  • Chimp - tests will be run with Chimp
  • Mocha - test will be written with in this framework
  • Chai - assertion library, it will help us assert test outputs with defined values
  • - it will control the browser

Creating tests

In your Meteor app create directory called tests. Any directory with name tests is not loaded by Meteor. See Meteor special directories.

Firstly we will need to abstract information about HTML page (under test) with page object pattern. Then we will create the test file itself. Before we start let’s get familiar with page object pattern first.

Page object pattern

Page object is a class which encapsulates logic of particular page. It stores DOM selectors and returns elements defined by these selectors. The reason why to have page object is whether UI changes, only pageObject should be rewritten and then tests should still work. It is DRY, because selectors are in one place in page object, and not in many places in tests. With page object test can be much explicitly written and therefore much simpler to understand.

More on page objects

Martin’s Fowler page object Page object in, ES5 code only:(

Page object and test Files

Note that these three files down below are just example files. You cannot get test working only by copying these files. You would also have to write down exact HTML code of tested page.


page.js is a base class which other page object classes will extend. In this particular code to get open() method working, you need to install url module:

$ npm install --save-dev url

More on using npm with Meteor.

// page.js

import urlModule from 'url';

export default class Page {

    // opens any of given relative path
    open(path) {
        browser.url(urlModule.resolve(process.env.ROOT_URL, path));
} extends page.js. It can contain any logic of real lesson’s HTML page. In this code browser.element() refers to instance and element() method. In Chimp browser object is global, you don’t need to import anything.

Note also that in client === browser


import Page from './page';

export default class LessonsPage extends Page {

    open() {'kurz-zakladni');
    get newLesson() {
        return browser.element('#new-lesson');

    get lessonNameInput() {
        return browser.element('#lesson-name-input');
    get newLessonOK() {
        return browser.element('#new-lesson-ok');
    get lessonName() {
        return browser.element('#lessonName')


Finally our test file lessonTest.js. We use mocha’s describe() and it() functions.

// lessonTest.js

import LessonsPage from './pageObjects/';

describe('On essons page', () => {
    let lessonPage = new LessonsPage();
    let lessonName = 'Test lesson 1'
    // this test has @dev annotation
    // it will be run in Chimp --watch mode
    // more details below
    it('you should create new lesson @dev', () => {;;
        // assert result with Chai


We will run tests with Chimp. It elegantly integrates with Meteor. Install it globally with npm:

$ npm i -g chimp

Run tests

Firstly start your Meteor app on port 3000 (default port).

$ cd my-meteor-app
$ meteor

Then run tests with Chimp. Remember have your Meteor app running and provide the correct path to tests with --path flag.

$ chimp --ddp=http://localhost:3000 --watch --mocha --path=chimp/tests

Witout --browser flag Chrome is set as default browser. Use flag --browser to run tests in other browser.

With --watch flag only tests with @dev annotation are run. Without --watch all test are run once.

Optional configuration file

Create config file to change behavior of

It can be handy to change time limit for waitForVisible() method. Default time limit is 500 ms, which can be sometimes too short.

// config.js
// it has to be ES5 export, otherwise it would not work with Chimp
module.exports = {
    webdriverio: {
        waitforTimeout: 2000

Pass config.js as a first argument to Chimp.

$ chimp chimp/config.js --ddp=http://localhost:3000 --watch --mocha --path=chimp/tests


With help of page object and other smart technologies we can maintain our acceptance test base with more ease. Test will become less fragile. Test can be run after each commit locally, which could be annoying after while. Better way is to set up CI environment to run tests there. In my next article, I want to explore this option as well.

Do you want to improve this article? Pass me a pull request.

Published 11 Aug 2016