Getting started - Attester documentation

Getting started

Attester is a tool written in JavaScript, to be run with Node.js and can be installed via npm.

It allows to run JavaScript tests written in any testing framework and execute them in any web browser, PhantomJS included.

Attester 1.x.x can only work with Node.js <= 0.8.0


To start testing your code you'll have to install attester in your project

npm install attester --save-dev

This will also modify your package.json to include attester as a devDependency.

If you want to make use of PhantomJS headless testing, you'll additionally need to download PhantomJS and make sure it's in your PATH.


attester has a command line utility that can be used in your build to execute your tests in a campaign.

Setup your project

Attester requires a configuration file that describes the list of tests and the available resources (source code to be tested).

Once you've created such configuration file you can modify your package.json and create a script to run attester.

The preferred script is test.

    "scripts": {
        "test": "attester test/attester.json"

Run attester

Once you setup your project you can run your campaign with

npm test

How attester works

Attester create a test server that awaits for incoming connections from different browsers. Every connected browser is a slave.

The test server dispatches pending tests to available slaves and gather the results in a common report. This allows to run JavaScript tests in as many browser as wanted.

In order to work, attester should be configured to know which tests to run, on which browsers, against which source code.

Configuration file

The configuration file describes the test campaign to execute. It can be either in the YAML (with a .yml or .yaml extension) or in the JSON format (with a .json extension).

There's no naming convention for the configuration file, so you can put it anywhere you like, preferably next to your tests.

The configuration file is comprised of the following parts:

A very simple configuration file in .yml is

# Specifies which files will be accessible through the web server:
        - 'lib'
        - 'src'

# Describes test configuration for each type of test
                - 'test/**/*.js'
        assertion: 'expect'

# On which browser the campaign should run
    - browserName: 'Chrome'
    - browserName: 'Safari'
      os: 'Mac OS X'
    - browserName: 'IE'
      majorVersion: 10

Further Reading

  • Campaign configuration with detailed information on how to describe your test campaign
  • CLI options with a description of all the options that can be used to configure attester behavior.
  • Attester as a module explains how to use attester as a module instead of a command line utility. This is the most advanced usage.
  • Developer documentation for the internals. It is useful to write custom plugins or to understand how attester works.