bd4638e95e When this happens, any useful feedback from the test results is lost, and the time invested in building up the test suite is wasted.. Setting up scenario-specific data 7.2.5. How will it benefit the business? Identify the business goals 3.4.1. Keep the step definition methods simple 6.2. Requirements analysis: discovering and understanding features 2.3.1. The "Given & When & Then" structure 5.2.4. Implementing the steps 6.8.4. Wording and semantics are important: the tests need to clearly explain the business behavior theyre demonstrating. Summary 9.
Understanding the business goals: Feature Injection and related techniques 3.1. What do you want to achieve? Start with a vision 3.3.1. The best automated acceptance tests tend to be the result of a collaborative effort between testers and developers. The Behave project structure 6.6.3. BDD is about writing specifications, not tests, at all levels 10.1.2. Many of these issues can be avoided if teams apply a few simple principles. Discovering the design 9.6. Using table data from step definitions 6.2.6.
Elmemb replied
447 weeks ago