Functionality, quality and ease of use of code coverage products vary significantly.
* Ant integration
Probably the most today are Java projects using Ant (or Maven) to manage their construction process, including running unit tests (or functional tests). Thus, the integration of Ant is one of those characteristics a code coverage can not afford not to have. However, there are subtle differences in how many goals related to coverage of code into a script. Yes, we will see some examples later. Of course, most of the tools also provide an alternative mode of autonomous operation of the analysis, either from the command line or via a GUI.
* Report formats
Another obvious feature coverage of code is the tool should have sex. Again, there are differences in the type and quality of reports supported. Some tools provide only textual summaries Ant console output, other produce enormous tables of names and numbers in HTML, and produce great images and others, others propose to make all this PDF format as well. We will see examples of the main types of reports in the next section.
* Source code link
Somewhat related to the previous question, the source code is something of a link can not live without once getting a taste of it. In practice, linking the source code means that, in the report code coverage, the tool has generated copies of the annotated source code, highlighting the elements that are not covered by your tests. I would not be surprised if this feature has been the greatest benefactor of code coverage tools to achieve critical mass. Before the code block which is the source of your coverage to stay away from "green" is much more effective than a method that contains a code that is not covered by the tests. All our examples include the link in the source code of their functionality.
* Controls
It does not take too long after that someone has introduced a rule where someone had launched the idea of applying this rule. It has also taken place in the code coverage. Some tools provide a way to pull the red flag, if code coverage drops below a given level. In the context of Ant integration, the script might not in general the construction until the tests have been strengthened to cover the bare parts of the code.
* History Reports
Few tools to collect a history of data protection and produce historical reports showing how your project code coverage has fluctuated over time. It is also a nice feature, although some might find it quite relevant.
Subscribe to this comment's feed
| < Prev | Next > |
|---|
