Monday morning, the build runs, all the unit tests, automated functional tests pass, and the tester goes to test the happy path of the user story, and it breaks first time. Despite our best efforts, we often find that assumptions, team processes, the move to automation, and even choice of terminology can create friction and frustration between developers, testers, and managers. This presentation looks at the role that developers, testers and managers each have in ensuring the quality of the software being created. It also looks at some of the common reasons why everyone has a different option on whether something is “done”, and how we can create a common understanding of what testing has been done, what testing needs to be done, and how the decision to ship should be made.
- Contact Us