You need npm installed (Node.js). Selenium-standalone is required for the UI tests (installed locally by npm). If you intend to run the tests locally, you'll need to update your Chrome browser and install the latest version of Selenium-standalone:
npm install selenium-standalone@latest
Not updating both Chrome and selenium-standalone can result in selenium not able to attach to the browser when running the tests.
💥💥 Do not commit your changes to the selenium-standalone version 💥💥
Run these commands to setup your dev environment:
npm install -g grunt-cli bower
npm install
bower install
Then to deploy the studio with the scheduler, create a symlink called studio in $SCHEDULING_HOME/dist/war
pointing to app.
- Fulfill the dependencies with
npm installandbower install. Then let's assume you did some changes to the code, you want to check for regressions. You need to either rungrunt clean build test:ui:dev(test is a predefined task of grunt, and already runs some syntax check on the code).
-
On the first run you need to use
node_modules/selenium-standalone/bin/selenium-standalone installwhich will install generic drivers and chrome drivers (firefox stopped support of their selenium driver and started a new webdriver in Rust). Once selenium server is downloaded, you can run it withnode_modules/selenium-standalone/bin/selenium-standalone startto start your local selenium server instance. -
Call nightwatch with your config and test suite
node_modules/nightwatch/bin/nightwatch --config test/ui/nightwatch.json --env jenkins-chromefor example
The test will assume you have a running studio instance (either in a real release that is running locally, or using method B). Method B doesn't require any running release, you have to run the following command node test/json-server-data/mock-scheduler-rest.js from your studio respository. Then you can run a single test file using node_modules/nightwatch/bin/nightwatch --config test/ui/nightwatch.json --test test/ui/specs/login.js --testcase "PWS-159 The dialog Please open a workflow appears behind the no workflow open panel"
if you don't specify the --testcase it will run the whole test file.
You can also run a mocked json-server to simulate a running instance of the Studio, of course nothing will be submitted or modified server-side:
grunt mock:run
or along with a full compilation:
grunt clean build mock:run