Please log in to watch this conference skillscast.
Want to improve your team's processes when it comes to acceptance testing? Daniel Wellman explores the technical and social forces that cause acceptance test suite to grow, and ways in which your team can refactor and improve such tests.
Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.
YOU MAY ALSO LIKE:
- Janet Gregory's Agile Testing for the Whole Team (in London on 28th - 30th October 2019)
- Uncle Bob Martin's Clean Code Workshop on Agile Software Craftsmanship (in London on 2nd - 3rd December 2019)
- P3X - People, Product & Process eXchange 2019 (in London on 31st October - 1st November 2019)
- DOODLE-DRIVEN DEVELOPMENT (SkillsCast recorded in May 2019)
- Crunching 'Real-Life Stories' with DDD Event Storming and Combining it with BDD Techniques (SkillsCast recorded in November 2018)