Experience as Embedded Tester in a Scrum Team
Everybody loves test automation, and everybody loves agile development. But they don’t always get along with each other. At the meeting of the Interest Group Tosca on 20 March 2018 an embedded tester in a scrum team of 15 shared his experiences with us – without sugarcoating the unpleasant details.
And there were quite many of them, like spontaneous changes which are being squeezed in during meetings but are not represented in a JIRA story and therefore cannot be tested and followed up. Or like the “classic” of agile development: The tester is testing a story – while the developer is already implementing a newer version of the story due to changes within the business requirements. What is the tester then supposed to do with his evidences out of his by now obsolete story? And how can the tester deal with the impossibility of setting-up long-term test cases when the database is fully erased with every development?
The speaker also looked at the developers who are permanently confronted with new requirements, too. He claimed stringent focusing and that always “Testing should be part of the story“, in everybody’s interest.