Software mall>development tool>Code quality management> Clover - Test code coverage tool

Commodity number:S20151116093374313

Clover - Test code coverage tool

Java and Groovy test code coverage tools

 

Product details Help document Purchase support Technical community
Clover  
Java and Groovy test code coverage tools

Clover provides a variety of indicators to balance the time and effort you spend on writing code and testing code.

 

Clover can run in your integrated development environment and continuous integration system, including the test optimization to make your test run faster and faster to find errors and vulnerabilities.

Authorization mode:
A Clover business license includes:
1 deployment of a single Clover instance on a server in a production environment;
2 create unlimited number of projects and problems;
3 permanent use of Clover;
12 provide 4 months of software technical support services - including new version update and email support;
5 to provide all the source code.
For more information, please refer toEnd user license agreement (END USER AGREEMENT ATLASSIAN).
 
What is the number of users:
User number refers to the number of users who are present in the application and have access to the application. The number of users here corresponds to the number of registered users who have access to the application, rather than the number of concurrent users (User Concurrent). If the application is open to anonymous users, anonymous users are not included in the number of users.
 
What is the host:
"Clover host" refers to a single physical machine running Clover, which is used to Instrument source code or generate coverage reports (including interactive reports via GUI or plug-ins).

bright spot

Find the risk of the code

Clover desktop terminal

Continuous integration

Test optimization

Groovy code coverage

 

bright spot

The safety code

Clover can identify the most risky code in your project so you can focus your attention on the most influential part of the test.

The desktop
Run Clover in Eclipse or IntelliJ to ensure that your recent code changes have adequate test coverage.
We build

Clover can integrate Bamboo, Hudson, Ant, Maven and other continuous integration systems, build automation tools, and to provide a code coverage report to build the results.

The test optimization
Speed up test execution in your build, faster delivery of impact feedback on recent code changes.
The Java also supports more than Groovy

Croovy also supports Clover, so you can find the risk of an automatic type code before the code is delivered to the end user.

 

Find the risk of the code

The cloud cover

Clover coverage of the cloud can quickly point out the most influential parts of the code in the new test.
- project risk - the most complex, minimum coverage of the class
- rapid success - maximum, minimum coverage of the class

The tree

Clover can help you quickly browse the code coverage of the entire project.
Color - on behalf of test coverage
Size - Code Complexity
Package hierarchy - display in a more understandable way

We each test code coverage

Clover tracking test and the relationship between the code in order to quickly identify:
- what classes and methods of test coverage?
- which test will cover a particular class, method, or line of code?

The trend report

Clover monitoring code coverage trends, in order to quickly identify new risks:
- new, not tested code.
- existing code coverage loss
Clover highlights that the code needs to be checked to resolve the risk
 

Clover desktop terminal

Support Eclipse&IntelliJ; IDEA
Clover can be run in any Eclipse based integrated development environment, or IDEA IntelliJ, to check the coverage of code changes before submitting the code to the source control library.
Color based visual test coverage annotation
- line in the source code file test coverage information
- a recent test run through and failure information
The continuous measure in the development environment
Clover desktop side provides a number of metrics and visualization to help you see them in the process of developing and testing.
- Clover cloud chart highlights the project risk and rapid success
Tree graph shows the coverage and complexity of the whole project.
- based on the built-in measurement method from the definition of metrics
 

Continuous integration

- Clover+Bamboo

Clover integrated Bamboo Atlassian continuous integration server, the results show that the test coverage metrics.
- the coverage of the process of building the trend shows that there can be found that there is a new risk
- test optimization is to speed up building by just running the test or previous failure of the test or previous failure to run the code.

The Ant, Maven and so on.

Clover can integrate most of the building systems, including:
- Ant
- Maven 2 & 3
- Grails
- Bamboo
- Jenkins
- Hudson
- line tools Command

The integration of Jenkins
One key can be built in the Jenkins continuous integration server to capture Clover code coverage information, identify project risk, through the Clover integration to real-time code coverage and test metrics.
- code coverage results in Jenkins structures
- view the Clover code coverage rate in the Jenkins weather report
 
 
Test optimization
The rapid test execution

Clover can be selected to test for speed up build and test execution:
- Test change code coverage
- where the failure of the building before the test

Let the test failed to appear as early as possible

The sooner a failure occurs, the more quickly it can be repaired. Clover can try to rearrange your test according to the following conditions:
- what code has been changed
- what tests have recently failed
What tests run the longest

The optimization settings
Through Clover, you can optimize your build, so as to adapt to the way you build, build content and build a running position.
- run only the changed test or test code that has been changed.
- run the tests first, and then run the other tests.
- random re arrangement of tests to rule out mutual dependency
- first run the shortest test
- run all tests on each N build
 
Groovy code coverage
The Clover and Groovy

You have started to use Groovy to quickly build applications? Clover can also measure the coverage of Groovy code!
Error properties and methods that are caused by input errors (such as "x.foo" rather than "x.foo")
- Clover supports Groovy closures
- Clover Grails plug-in to get the code coverage of network applications

The integration of Grails
Clover-for-Grails plug-in can be generated from the Grails network application development framework Clover code coverage report. It provides detailed information that can highlight the low coverage area of the project to guide you to make informed decisions based on automated test strategies.
Spock framework support

Clover can be closely integrated with the Spock framework in the edit and test execution, especially Clover can identify the descriptive name of the test, such as this "is my test def" and the processing of @Unroll notes as well as test iterations. Thanks to this function, the test uses a number of variables that can be used to define the true meaning of the name (e.g., "of minimum 5 and 3 is 3") to define the variables (e.g., minimum "of #a #b and is #c def").

If you have an urgent need to communicate, please call010-57410251, or online consulting customer service QQ Click here to send me a message.

Published consultation:

Advisory reply time for the working day as early as 9:00-18:00, please be patient and wait for staff to respond, if you have a problem to need emergency communication, please dial the phone010-57410251.

Consulting content:
submit
commonZeroTopic discussionPublish a topic