Developers know that unit testing, coverage and code measurement is an important part of any development effort, yet only 20% of companies do this. Why? Because it's hard, time consuming, and expensive. Until now ...
With the CoView family of plug-ins, companies set their own quality goals and use our plug-ins to meet them. Want to automate JUnit? We can do that. Want to develop testable code? We can help there too. Want to measure path and branch coverage? We got you covered.
Read more ...
| CoViewDeveloper | CoViewManager |
|---|---|
| Develop Testable Code | Measure Code Testability |
| JUnit Designer | JUnit Metrics |
| JUnit Wizards | One-Click Analysis |
| Detailed Code Coverage | Code Coverage Summary |
$99/user/year |
$199/user/year |
Supports Eclipse 3.1, 3.2 & 3.3RC, JDK 1.4, 5 & 6, JUnit 3.8 & 4
| Excuse | Solution | |
|---|---|---|
| Sales wants software now, so unit testing and coverage takes a back seat |  |
CoView helps make your code more testable through metrics, unit test automation and code coverage |
| Meeting requirements on time is hard enough | |
CoView lets you meet requirements AND create testable code, on time |
| Customers expect bugs, why not deal with bugs then? | |
Not only do bugs cost money, they also have an opportunity cost - instead of fixing bugs, you could develop new features. CoView lets you create testable code and JUnit tests using your standards, reducing the cost and time required to find and fix bugs |
| Excuse | Solution | |
|---|---|---|
| I know Test Driven Development (TDD) is good, but I don't have time to learn it. I have too many fires to deal with | |
CoView provides products that support TDD and DTT (Develop Then Test) methodologies - you can put your fires out faster |
| My code and environment are too complicated to truly unit test - that's why we have testers | |
CoView's finds the most critical paths and creates most of the JUnit test for you |
| I don't have time to unit test | |
You wrote the code, so you should - CoView can help save you up to 75% of your time and get better results |
| Excuse | Solution | |
|---|---|---|
| Code Coverage is a commodity - lots of companies provide coverage products | |
So does CoView, but CoView also provides branch and real path coverage (not just say we do), and we make the process easy for you |
| Coverage is coverage - what's the big deal? | |
There are differences in coverage: path coverage is great, branch coverage is good, and statement coverage is better than nothing |
This image shows you the new testability feature. You can see the calculated metrics are colored based on the severity. In this example, the method instanceMain has 56 lines of code, 12 cyclomatic paths and 13 combined paths. The yellow background indicates that the lines of code (56) was greater than the threshold (50), with a severity of 'warning'. CC Paths (12) exceeded the threshold (10), and the severity was red.
This image shows you how we highlight paths through a method. In this particular case, data can travel through any of these 5 defined paths. Path 4 (in the example), shows you the decisions being executed in association with their state. Red decisions execute false, green decisions execute true.
This image shows you how we identify total paths and tested paths. The top pane describes how tested paths/total paths, and the bottom pane lists the paths in bold which were executed.
