protractor-cucumber-rerunner

Reruns failed cucumber-protractor test by saving all the Cucumber scenario tags of the failed tests. All the saved tags are picked up and used as parameters in the consecutive Protractor run command.

Issue solved with this solution Other solutions strucle with timeout issues - especially cucumber steps timing out prove to be an issue. By adding the tag to the rerun command and only removing it when the scenario related to the tag has specifically passed, leaves all the failed tags in the rerun command even if the After in the hooks module is not called.

Basic flow

1. Test starts, Before is called in the hook.js file;
2. Tag of the Cucumber scenario is stored;
3. Test scenario runs;
4. Test ends, After is called in the hook.js file;
5. If test passed - tag of the scenario is removed;

Requirements for the cucumber scenarios

• All the cucumber scenarios need to have a tag;
• A scenario can have multiple tags but the first will be used to rerun the scenario if it has failed;
• The first scenario is unique;
• Scenarios can run and pass independently of eachother;

Although preferably the first scenario tag is unique, it doesn't have to be. If a scenario fails with a tag that is not unique the rerun program will execute all scenarios with this tag even if the scenarion did not fail.

Example:

@unique-scenario-tag
Given I am here
  When I do this
  Then I see that

Getting started

Follow the steps below to get started with the project:

Clone the project:

$ git clone https://github.com/onno-amsterdam/protractor-cucumber-rerunner.git

Install dependencies

$ npm install

Run the tests

To run the test first start protractor:

# to update the webdriver:
$ npm run prestart-webdriver

# to start the webdriver
$ npm run start-webdriver

Then in a new terminal.

To run the tests use the CICD scripts in the cicd_scripts folder. Run the scripts from the projects root folder with these commands:

$ npm run test:rerun

This will start running the tests. Some of the tests are deigned to fail to make sure the failed tests are picked up and rerun again.

Or you can run the tests and rerun the failed tests separately.

To run the test without rerunning failed tests:

$ npm run test

Now if there are failed tests you can do two things, the first is to go into the rerun-command folder and open the rerun_command.txt file, copy the protractor command and run it in the terminal. Only the test scenarios with the failed tags will be run.

Second is to run the rerun the failed scenarios with the following command:

$ npm run rerun

Contributing

Feel free to contact the author if you want to collaborate on this project.

Authors

• Onno van Piggelen - Initial work

License

This project is licensed under the MIT License - see the LICENSE.md file for details