Writing end to end tests with a smile
summary
Team replaces noisy UI checks with Cucumber (BDD) plus Nightwatch (Selenium) and Gherkin feature files so acceptance criteria become executable scenarios. Tests move from giant brittle scripts to small reusable steps, developers reuse step implementations via JBehave so Java teams avoid learning JavaScript, non‑technical product people author scenarios, CI shows green/red status clearly, and the suite focuses on a few critical journeys so runtime and maintenance drop while confidence in releases rises.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:40Hello from Kim
- 2:05Understanding end to end testing
- 2:40Tools
- 3:06Automation
- 3:40Keyword Optimization
- 4:33Functionality
- 5:00Roadmap
- 5:22Why testing
- 6:32Java application
- 6:50Java backend
- 7:17UI
- 7:30Product Team
- 8:05Frontend Testing
- 8:40Concerns
- 9:18Show of hands
- 10:17Back to make
- 11:15What is a good strategy
- 12:00Vision of the perfect world
- 12:35What we learned
- 13:02First step
- 14:54User stories
- 15:27User story dashboard
- 16:35Cheating
- 17:03Noise
- 17:36Nightwatch
- 18:38BehaviorDriven Development
- 21:03Syntax
- 22:03Java Code
- 23:17Output
- 26:42Summary
- 29:31How do we change
related talks
25mWriting end to end tests with a smile
30mWriting end to end tests with a smile
45mLet's talk about software behaviour (BDD)
09m"Effective ways of using BDD concept for Testing"
36mBDD With Cucumber
42mBDD Tests: Have Your End-to-End Tests Written for You
58mTesting Strategy - New Model, Better Outcomes
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier