Webcast: Empowering Continuous Testing through Behavior-Driven Development
Continuous testing has sped up the development lifecycle and provides immediate insight into any would-be business risk, but automating tests is neither cheap nor easy. Teams face the challenges of having to find out why a test failed and how to fix the problem, automating tests in time for them to be useful, and overcoming the lack of technical team members who can write automated tests.
Behavior-driven development (BDD) combines collaboration and automation so the team is laser-focused on the desired behaviors of the product before writing any tests. With BDD, product owners, developers, and testers work together to define behavior scenarios using given-when-then constructions. Each scenario is mapped to executable code, so knowing which behavior failed will help pinpoint where the code is broken. Many given-when-then scenarios also can be reused, which speeds up testing time and allows nontechnical testers to automate tests because there is no coding required.
We discuss how BDD reduces ambiguity and helps ensure a product will satisfy the customer’s business requirements with an acceptable level of business risk upon release.
You will learn:
- How to confidently take the next steps toward implementing BDD
- How to write effective given-when-then scenarios
- The key differences between manual testing scenarios and continuous testing scenarios
- How BDD amplifies the benefits of continuous testing
- The best tools, resources, and frameworks to help you get started
About the Presenters:
Andy is a software engineer and consultant who specializes in building test automation solutions using the latest technologies and best practices. He is currently a Software Engineer in Test at PrecisionLender and also runs a tech blog at AutomationPanda.com.
Josh leads Cycle's Product Development team, determining strategic vision and priorities for Cycle's software offerings. In this role, he oversees Cycle's roadmap, team development, product vision, user experience, and product culture.