Timeline for depth vs. breadth
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2013 at 16:33 | comment | added | Suchit Parikh | Well, what I used to do is assign the testers their 'primary' set of cases that they take accountability for & the rest of the cases, they can take a look once they are done with their primary set of TCs. But make sure they understand their task is not limited to primary set. You can obviously tweak it as it works the best for you | |
| Apr 11, 2013 at 14:05 | vote | accept | ph33nyx | ||
| Apr 11, 2013 at 14:05 | comment | added | ph33nyx | The testing group all know the entire system. I will stick with assigning by browser/platform. Ancillary question: I like your suggestion about having each tester focus on different test cases. I am thinking if I have all test the most critical scenarios, I can give each person a different set of outlying test cases. Does that sound about right? I worry about the risk of missing things that only go wrong on one browser/platform. | |
| Apr 9, 2013 at 21:55 | history | answered | Suchit Parikh | CC BY-SA 3.0 |