Timeline for Tool to minimize tests number and maximize code coverage
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2014 at 1:44 | history | edited | user246 |
edited tags
|
|
| Oct 21, 2013 at 20:00 | answer | added | Sam Woods | timeline score: 1 | |
| Oct 21, 2013 at 12:32 | history | tweeted | twitter.com/#!/StackSQA/status/392267099961569280 | ||
| Oct 20, 2013 at 8:49 | comment | added | dzieciou | biggdman, note that maximizing code coverage is not the same as maximizing test coverage. You may have ideal code coverage while still important test cases not covered. | |
| Oct 20, 2013 at 8:34 | history | edited | dzieciou | CC BY-SA 3.0 |
Made a title more generic
|
| Oct 20, 2013 at 8:22 | history | edited | dzieciou | CC BY-SA 3.0 |
Added link to the mentioned tool
|
| Oct 20, 2013 at 8:12 | answer | added | dzieciou | timeline score: 2 | |
| Oct 19, 2013 at 12:40 | comment | added | user246 | I don't know of any tools that use code coverage metrics to help you select a reduced test data set. There are ways to generate a reduced test data set for combinatorial testing problems. See sqa.stackexchange.com/search?q=combinatorial+testing for details. | |
| Oct 19, 2013 at 11:05 | review | First posts | |||
| Oct 21, 2013 at 1:01 | |||||
| Oct 19, 2013 at 10:49 | history | asked | biggdman | CC BY-SA 3.0 |