Timeline for Why does the Scrum guide say no testers?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| Dec 14, 2012 at 18:04 | comment | added | martiert | @Maxood: Testers should, in my opinion, not touch unit tests. They should work on acceptance tests, in cooperation with developers, and have responsibility for the manual/GUI testing. The unit testing is on a level that is only interesting for the developers. The test pyramid (blogs.agilefaqs.com/2011/02/01/inverting-the-testing-pyramid) also has responsebilities, Unit-testing=developers, acceptance testing = shared, GUI testing = testers. | |
| Dec 14, 2012 at 16:44 | comment | added | Maxood | @MichaelBorgwardt Very true! But what if you find your tester busy in unit testing which is primarily a developer's job? I feel the former option should only be availed when it comes to code optimizatiion and application scalability, etc. What do you say? | |
| Dec 14, 2012 at 16:29 | comment | added | Michael Borgwardt | @Maxood: I'd say that TDD most definitely doesn't make manual testing superfluous. If something becomes an issue, you solve it; you don't start avoiding it. | |
| Dec 14, 2012 at 16:25 | comment | added | Maxood | TDD would be a better approach for startup teams. I have strongly felth that when testers and developers work together in novice teams, testing becomes an issue. What do you say? | |
| Dec 14, 2012 at 16:11 | history | answered | ChrisF | CC BY-SA 3.0 |