Cognifide default setup for Puppeteer and Protractor tests
npm install @cognifide/e2e``bash`
$ npm install @cognifide/e2e --global
`bash`
$ coge2e init
Running this command will init setup and allow to select which configuration should be added.
npm run test
There are two ways to run Protractor tests on specific environment: one way is to add another parameter . List of available environment you an find in /data/env.json. The second way, easiest, is to run specific npm script: by default, configuration comes with 4 environments:
- local - default environment which is tested when npm run test is executed
- dev
-
- In order to run tests on, for example, on
environment simply run npm run test:prod
npm run test --params.env staging
/ or /
npm run test:staging
Real life example:
npm run test
--suite homepage
--exclude tests/analytics/homepage.js
--params.env prod/ or /
npm run test:prod
--suite homepage
--exclude tests/analytics/homepage.js
$3
* Get familiar with technology stack:
* https://www.protractortest.org/
* https://jasmine.github.io/
* Read about:
* Page Objects
* Styleguide for ProtractorPuppeteer & Jest setup
$3
Similar to Protractor config, default configuration comes with 4 default environments:
-
- default environment which is tested when npm run test is executed
- dev
-
- Tests can be run on specific environment by running scripts like
. The only difference is that it's not possible to pass arguments like --params.env prod to the script, so trying to run npm run test --params.env prod` will result in error. The only acceptable arguments are those that are available for Jest CLI options.