Please log in to watch this conference skillscast.
Are you drowning in Cucumber scenarios? Do they take too long to run? Do you spend a long time to fixing them when they fail? Are they costly to maintain when your system evolves? Do they suck as documentation? These symptoms usually arise from a deeper problem: The system isn't designed for testability and evolvability, and both the system and test code is too tightly coupled in places where they ought to be loosely coupled.
In this talk Aslak will teach you some architectural patterns that will help you achieve faster tests that are easy to fix and maintain, and work as great documentation.
YOU MAY ALSO LIKE:
- Sub-Second TDD with a Dash of Honey (SkillsCast recorded in October 2017)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- Domain Models in Practice with Marco Heimeshoff (Online Course on 8th - 12th March 2021)
- DDDx — Domain-Driven Design eXchange 2021 (Online Conference on 8th - 9th June 2021)
- P3X — People Product Process eXchange 2021 (Online Conference on 15th - 16th September 2021)
- Strategic Domain-Driven Design Tools For Non-DDD People (SkillsCast recorded in October 2020)
- Lightning Talk: Specification as a Library (SkillsCast recorded in October 2020)
Designing for Evolvability
Aslak Hellesøy is the creator of Cucumber and co-founder of Cucumber Limited. He is a co-author of The Cucumber Book and an early adopter of XP and BDD. Aslak works as a programmer, software architect, business owner and trainer in a variety of industries, including finance, telecom and retail.