Running the tests
If you need to go further with attester, you can read the full documentation on http://attester.ariatemplates.com/.
To start testing your code you'll have to install attester in your project
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.
A simple configuration file is available below.
It is also possible to use a separate script for attester instead of test, this gives you the flexibility to run more scripts from npm test.
Attester requires a configuration file (see the Configuration file below) that describes the list of tests and the available resources (source code to be tested).
This configuration file can be either a json or a yaml file.
Once you've created such configuration file you can modify your package.json to reference it under
script.test sand create a script to run attester.
The preferred script is test.
The configuration file describes the test campaign to execute. It can be either in the YAML (with a
.yaml extension) or
in the JSON format (with a
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: For more information on the campaign configuration file and the complete list of properties please refer to this article
A very simple configuration file in
Once you setup your project you can run your campaign with
Attester create a test server that awaits for incoming connections from different browsers. Every connected browser is a slave.
In order to work, attester should be configured to know which tests to run, on which browsers, against which source code.
- 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.