- Add dependencies to package.json and install.
..."nemo": "^1.0.0""nemo-eyes": "^0.0.4"...
nemo-eyesplugin to your nemo config JSON object. Also note
"driver":..."plugins":"eyes":"module": "path:../""arguments":"sdk":"setApiKey": "env:applitools_api_key""setBatch": "desktop""setForceFullPageScreenshot": true"viewport":"width": 1200"height": 600"mock": "env:applitools_mock"
How to use
Once nemo-eyes plugin is registered,
eyes namespace will be attached to
nemo and methods for visual testing are exposed. Idea is to,
- Initialize your application and test using
nemo.eyes.open('Sample Application','Homepage test');
- Trigger a visual check using
nemo.eyes.checkWindow("PayPal Home Page");. If base image for the window in question is present, new screenshot will be compared against it. Otherwise new screenshot will be saved as a base image
- Close test and resolved promise will have corresponding results
Configure nemo-eyes via the
arguments section in the plugin configuration as above.
For any Eyes SDK method that can takes string arguments, you can program the Eyes SDK via the
sdk section of the
If you supply
"mock": true or
"mock": "true" via the config (as shown above), you can run your scripts without having to
duck-type around the eyes calls in your script. This is handy if you're working on other aspects of your script and do not want
to incur cost or any latency associated with calling out to Applitools.
Running a sample visual test using Applitools.
- In order to run a test you need to have an Applitools account (free track is available).
- Copy your API key from the tutorial page (choose "Automated visual tests", then scroll down to step 4), and set it in nemo
- go to the repository's root folder and run