Suggest modification to this talk

Title

Description

The BDD hype cycle is over. Recently, there's been a lot of backlash against popular BDD libraries like Cucumber. Some developers blame their test frameworks for brittle test suites and long build times. Others go so far as to claim that acceptance testing is simply not sustainable, period. In this talk, we'll do some root cause analysis of this phenomenon with shocking results - it's not the test framework, it's not the methodology, it's you. You've abused your test framework, you've cargo-culted the methodology, and now you're feeling the pain. We'll show you a way out of the mess you've made. We'll discuss the main problems BDD was intended to solve. We'll show you how to groom your test suite into journey, functional, integration, and unit tests in order to address build times. We'll teach how to mitigate against brittleness and flickers, and how to let your tests reveal the intent of the application and actually become the executable documentation we've been waiting for.

Help us caption & translate this video!

http://amara.org/v/FGc1/

Date

Summarized using AI?

If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.

Show "Summarized using AI" badge on summary page

Summary

Markdown supported

In the talk "It's not your test framework, it's you" presented at LA RubyConf 2013 by Robbie Clutton and Matt Parker, the focus is on sustainable practices in Behavior Driven Development (BDD). The speakers highlight the backlash against popular BDD frameworks like Cucumber, attributing issues with brittle test suites and slow build times to the misuse of these frameworks rather than to the tools or methodologies themselves. They advocate for a deeper understanding of BDD's intentions and emphasize that poor practices lead to complications in testing. Key points discussed include:

- **Hype Cycle of BDD**: The initial excitement around BDD saw aggressive adoption, followed by criticism and a decline in practice as developers encountered challenges.  
- **Common Issues**: Problems such as brittle tests, insufficient acceptance criteria, and slow performance plague many implementations.  
- **Cargo Cult**: Developers often imitate methodologies without fully understanding them, leading to ineffective testing.  
- **Importance of Conversations**: Engaging product managers in detailed discussions about feature specifications is critical to success. This approach aligns development efforts with user needs.  
- **Tools Evolution**: The transition from early BDD frameworks to more sophisticated tools like Cucumber and features like Gherkin illustrates the need for a shared understanding and language between developers and product owners.  
- **Reducing Brittle Tests**: Tests should focus on what the application intends to do rather than how it operates, which reduces dependencies on the UI and enhances stability.  
- **Living Documentation**: BDD aims to create clear documentation that's meaningful and helpful throughout development.  
- **Performance Optimization**: To ensure efficient testing, teams should regularly review and optimize their test suites to prevent long execution times and improve CI workflows.

The presenters conclude by stressing the importance of treating tests as essential components of development and inviting developers to approach BDD with a commitment to continuous improvement and active engagement with product owners. By focusing on how tests reveal application intent and by employing best practices, teams can navigate the complexities and challenges of BDD more effectively, leading to better software quality and user satisfaction.

Cancel