How to get Automated Testing “Done”
Test automation has been around almost as long as software has been developed. In the age of Agile and the DevOps arena, having tests fully automated is increasingly becoming a key factor to the success of a project. The best place for the creation of tests is the agile sprint team, where product owners, developers and QA’s work together. Tests and their automation should be ready when a sprint is “done”. However, more often than not teams find themselves in a situation where the functionalities under test are ready, but the tests are not.
In this webinar, Hans goes through a number of solutions a team can do to diminish this problem, and what actions to take when it happens. Hans discussed the following solutions on how one can apply better test design to drive better automation, a number of technical strategies, what developers and product owners can do to help, and how to handle the testing and automation work that is still left after a sprint has finished. A key item in handling the test automation work that is left over is that QA’s need to own the testing from the beginning, and should not get stuck in the work of previous sprints, since that will inhibit good cooperation with other team members, making matters worse.
- Get more tests created and automated.
- Make automation manageable and maintainable.
- Keep the QA people in sync with their fellow team members.