Writing end to end tests with a smile
summary
The team reports a concrete pipeline: Cucumber added to Nightwatch (Selenium), feature files with user stories in feature files and small reusable step definitions, Jenkins running the suite, and developers implementing steps in whichever language they prefer. Acceptance criteria live with code so tests show readable pass/fail sentences instead of noisy DOM dumps, test scenarios stay short to keep runtime small, non‑technical staff contribute Gherkin stories, and the process measurably reduces ambiguity and maintenance effort.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:24edit an acceptance criteria
- 8:09see the output of the nightwatch test runner
- 9:10write user stories with test scenarios
- 9:36implement small steps instead of huge blocks of code
- 10:03adding cucumber
- 17:00update user stories and cucumber tests
- 18:25set up your own testing process
related talks
34mWriting end to end tests with a smile
30mWriting end to end tests with a smile
42mBDD Tests: Have Your End-to-End Tests Written for You
36mBDD With Cucumber
47mTelling Better Stories with Tests
41mEnd-2-end testing without the pain
35mCucumber: Automating the Requirements Language You Already Speak
44mSelenium and Cucumber