There is a quite extensive suite of Unit Tests that are provided along with the code to help your development.
You can execute them in two flavors:
- Single run (this is the same flavor that is used on Jenkins):
- Watch mode:
npm run test:auto
While developing the GUI we'll suggest you to run the test in watch mode, and they'll be executed anytime a file changes. It will help you in catchings bugs immediately. It also provide more information on which tests are executed.
End to End Tests
There is a suite of basic end to test that are defined using protractor, an AngularJs oriented version of Selenium.
These tests can be found in the
Run the tests
NOTE: These tests are designed to work with the Mock R-CORD config
npm run test:e2e
Other paramenters you can pass are:
|UI_URL||Address of the GUI (deaults to
|UI_PWD||Password to login (needed only for remote connections)|
|TIMEOUT||Time allowed for each test|
|PT_ARGS||Extra arguments for Protractor, eg: "--suite dashboard" (Suites are defined in
|PT_CONF||The path of the config file (eg: "./conf/protractor.conf.js")|