This is a demonstration of integration TestCafé into CucumberJS tests using TestCafe and Cucumber.

Big thank you to helen-dikareva for your help in starting the integration with your repo. This is a fork of all of the hard work you've put in.

Also, thanks to the team at TestCafé for allowing testers to break away from Selenium.

Depreciation Notice - There are talks to officially support the Gherkin syntax in TestCafé. Once those changes are in place I will no longer support this repo. Please voice your support of these changes becoming native to TestCafé.

1. Make sure Node.js is installed
2. Navigate to the root of the repo
3. Use the npm install command

You can run tests by executing the .\node_modules\.bin\cucumber-js.cmd or npm test commands in command prompt

You can run tests by executing node_modules/cucumber/bin/cucumber-js

• Initial Setup
  • Debuging in VSCode
• Using TestCafé
  • Creating your first test
  • Selectors
  • Actions
  • Assertions
• TestCafé & CucumberJS
  • Helpful VSCode Setup
  • Creating Features
  • Creating Step Definitions
  • Adding TestCafé Functionality to Cucumber steps
  • Harnessing Cucumber's Power
  • Page Object
  • Running Tests
  • Reporting and Taking Screenshots

• As of the time I am writting this, there is only 1 passing test of 3. I decided to not make all of the tests passing, so you could see how failures are handled.

• My solution closes the TestCafé browser between each scenario. I tried to keep it open between scenarios but had trouble with handling failures. If you find a solution, I'd like to know.

• With TestCafé version 0.19.0, you no longer have to manually update stack-chain. Thank you to the TestCafé crew for making the integration much easier.

Thanks to everyone who has contributed to this project over the last few years.