Timeline for Recommendations for code coverage tools?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2013 at 15:37 | comment | added | Shantonu | Thanks to all for you comments.I thought it partially. Now I see the clear picture. I have already started looking sonar. | |
| May 5, 2013 at 23:28 | comment | added | corsiKa♦ | I think one of the key issues here is explaining how it relates instead of just listing them. For example, there may be some JUnit or NUnit plugin that you can use to get what you want, but without that extra knowledge it isn't as useful. | |
| Apr 30, 2013 at 22:08 | comment | added | user246 | @Shantonu I think Sam was asking about tools that measure how much of the code under test is executed. The packages you described are frameworks for organizing and executing automated tests. To see the difference, try comparing ncover.com to nunit.org. | |
| Apr 30, 2013 at 21:30 | comment | added | testerab | Still not clear to me how your answer relates to Sam's question? | |
| Apr 30, 2013 at 19:50 | comment | added | Shantonu | Actually Unit tests can test your codes before building any solution and you can cover code coverage (along with decision coverage). I thought of code coverage as tested code. | |
| Apr 30, 2013 at 19:49 | review | Low quality posts | |||
| May 5, 2013 at 23:30 | |||||
| Apr 30, 2013 at 19:33 | comment | added | Sam Woods | Can you expand your answer? How do mstest, nunit and junit resolve my needs for code coverage? | |
| Apr 30, 2013 at 19:30 | history | answered | Shantonu | CC BY-SA 3.0 |