Timeline for How much should a tester understand and rely on implementation details?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 25, 2014 at 19:31 | answer | added | Bj Rollison | timeline score: 4 | |
Mar 24, 2014 at 11:49 | answer | added | Kate Paulk | timeline score: 4 | |
Mar 24, 2014 at 10:43 | history | tweeted | twitter.com/#!/StackSQA/status/448047454450356224 | ||
Mar 24, 2014 at 8:39 | answer | added | amazpyel | timeline score: 2 | |
Mar 23, 2014 at 20:36 | answer | added | dzieciou | timeline score: 4 | |
Mar 23, 2014 at 20:04 | comment | added | Joe Strazzere | I don't understand what that means? You want them to test with fewer plans for you to review? What does the number of test plans have to do with understanding code or relying on implementation details? | |
Mar 23, 2014 at 20:02 | comment | added | user3251930 | Well, I have to review more test plans and test that I would have liked to. | |
Mar 23, 2014 at 20:00 | comment | added | Joe Strazzere | Ok. So you are the manager, and you wonder if your team should be testing differently than they currently do. So - how are the results? Without regard to how they test, how effective are their tests? Are they finding bugs, or are important bugs making their way into production? | |
Mar 23, 2014 at 17:41 | history | edited | dzieciou | CC BY-SA 3.0 |
added 2 characters in body
|
Mar 23, 2014 at 17:11 | answer | added | Jeff_Lucas | timeline score: 8 | |
Mar 23, 2014 at 16:44 | history | asked | user3251930 | CC BY-SA 3.0 |