Timeline for Examples and Best Practices for Seeding Defects?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 14, 2015 at 0:30 | history | suggested | Pierre.Vriens | CC BY-SA 3.0 |
Retagging for system tag "untagged"
|
| Jun 13, 2015 at 6:06 | review | Suggested edits | |||
| S Jun 14, 2015 at 0:30 | |||||
| Jul 11, 2013 at 18:13 | history | tweeted | twitter.com/#!/StackSQA/status/355389458071302145 | ||
| Jul 6, 2013 at 22:28 | history | migrated | from programmers.stackexchange.com (revisions) | ||
| Jul 1, 2013 at 17:17 | answer | added | Frank Hileman | timeline score: 2 | |
| Jun 30, 2013 at 22:34 | answer | added | EdH | timeline score: 2 | |
| Jun 24, 2013 at 16:57 | comment | added | Robert Harvey | @ThomasOwens: Create a branch or diff in your source control system that only includes the seeded defects. | |
| Jun 24, 2013 at 14:04 | comment | added | Thomas Owens♦ | I've never used defect seeding, but I suspect the problem is one that McConnell pointed out: you may forget to remove you seeded defects. The places that are best served by using defect seeding to determine the effectiveness of their testing processes are also the places that would be most impacted by leaving a defect in the system. I can think of ways to mitigate this problem, but it still comes down to a question of time and budget to deal with the seeding and testing not only the seeded code, but the unseeded/releasable code. I would like to here from someone who has tried it, though. | |
| Jun 24, 2013 at 12:14 | history | asked | MathAttack | CC BY-SA 3.0 |