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:
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 1st - 3rd October 2018)
- Jenny Martin and Pete Buckney's BDD From Start to Finish - Successful Delivery through Continuous Collaboration (in London on 5th - 7th November 2018)
- P3X - People, Product & Process eXchange 2018 (in London on 8th - 9th November 2018)