Delivering test automation in-sprint – before the developers finish writing the code – delivers far more value than test automation delivered later. Delivering in-sprint lets the developers run all of the tests before they open a pull request, so they find and fix the bugs before QA ever gets the code. This is a win-win-win – it significantly improves developer and QA efficiency and delivers new features faster with fewer bugs, making the product owner and the customers happier too!
Takeaways from the topic:
- How to implement Specification by Example/BDD as a development methodology, not as a tool.
- If you are writing test scripts you have already failed.
- How to write – and automate – requirements.
- Zero test cases, zero test scripts, and lots of automation are the right way to go.
- How to reuse your automation across interfaces – use at least half of the automation code for the web, the API, and the mobile apps.
- Cut the cost of maintaining your automation by 50% to 80%.
June 6 @ 10:45
10:45 — 11:30 (45′)