Timeline for Should QA report bugs on features before they are fully implemented?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2016 at 14:48 | history | edited | Peter M. - stands for Monica | CC BY-SA 3.0 |
added 250 characters in body
|
| Feb 4, 2016 at 0:25 | comment | added | testerab | Like @MichaelDurrant, I have worked with developers during feature development, testing partially complete work. It works very well indeed, even if I am not pairing with the developer, as long as we talk together instead of through the bug tracker. The biggest benefit of this is that my understanding of what we're building grows alongside the developer's, and I can feed in my questions about use cases as they're building. | |
| Feb 1, 2016 at 12:53 | comment | added | RubberDuck | @MichaelDurrant a QA pairing with a dev is a bit different in my opinion and not what I gathered from yourcomment here. If that's the kind of thing you're talking about, then yes. I could certainly see your point. | |
| Feb 1, 2016 at 12:46 | comment | added | Michael Durrant | "ready to be tested" tends to lead to code that is already starting to "set" | |
| Feb 1, 2016 at 12:45 | comment | added | Michael Durrant | @RubberDuck Insane or not, in reality I have worked in multiple organizations where, as QA pairing with developers on testing during feature development, this has led to less bugs; better features; fewer regressions and better code. Insane or not, that's been my real world experience. I've also worked where testing was more separated and I've seen how much harder, longer and more costly it was to fix errors, especially small minor ones. I love being able to turn to a dev and say can you fix x and 30 seconds later it's done and I grab the updated code. Your mileage may (and seems to) vary. | |
| Jan 31, 2016 at 11:45 | comment | added | RubberDuck | @MichaelDurrant that's insane, even with an "agile" methodology you don't want people wasting time testing things that aren't ready to be tested. | |
| Jan 30, 2016 at 0:55 | comment | added | Michael Durrant | This is true in a waterfall approach but not in a good Agile approach | |
| Jan 29, 2016 at 15:12 | history | edited | Peter M. - stands for Monica | CC BY-SA 3.0 |
added 267 characters in body
|
| Jan 29, 2016 at 15:05 | history | answered | Peter M. - stands for Monica | CC BY-SA 3.0 |