Pros and Cons of Automating Cucumber Test Scenarios with Frequent Releases
summary
Examines pros and cons of using Cucumber for automating test scenarios in projects with frequent releases, focusing on whether Cucumber’s features support effective cross-team collaboration. Discusses trade-offs of Cucumber-based test automation (readable Gherkin scenarios, mapping to step code, maintenance cost) and considerations for tool choice when releases are frequent.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:53Test maintenance issues
- 3:37Cucumber and Gherkin clarity
- 6:06Developer benefits
- 8:13Code reuse
- 10:18Test maintenance
- 12:48Early scenario writing
- 14:31Step definition issues
- 17:01Cucumber best practices
- 20:10Automation tools
- 21:15Adopting Cucumber
- 22:21Q&A
related talks
36mBDD With Cucumber
35mCucumber: Automating the Requirements Language You Already Speak
40mHow Cucumber Can Improve Your Testing
09m"Effective ways of using BDD concept for Testing"
16mCucumber Tests: Legends and Reality
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier
19mBusiness Impact Delivery Using Test Automation
34mWriting end to end tests with a smile