Robert Sabourin shared his test practices in the scrum team in the out of the frying-real-world stories of scrum migration-and no one got badly burned article. Traditional tests are probably divided into two types of positioning: (1) "goalkeeper": Quality champion, blocking the release of unreliable, ineffective, and bug-filled versions. (2) "information provider": provides a large number of positive information about the status of project development. Tell everyone which functions are working normally, which functions are not working properly, and which bugs must be handled. In the scrum team, the boundaries between testing and development become blurred. Some people mainly do the testing work, while some people mainly do the development work. However, during the rapid development process, everyone will be called for testing or supporting testing. Testers work with developers. testers are both consultants and active participants. Before writing the code, the tester and the developer work together to determine how the code is correctly implemented and works properly. Before writing code, write detailed "story" Test details. This is a process that combines requirement analysis and design. Testers help developers decide how to meet the "story" requirements.
