Now cobertura will generate HTML and XML report automatically in a directory named test-result/code-coverage/ in your project home where your shutdown the server. That’s also works with Continuous integration like Jenkins.įor switch in this mode you can delete properties % or switch them to true. Now, more interesting use case, is to run cobertura at the end of test process with command play auto-tests or play test ( follow by ctrl+c for shutdown play ) And now you can see html report in iframe or directly on file:/path/to/your/application/test-result/code-coverage/.Ĭode coverage is directly calculated when you running the tests – each test you run will add coverage to your Java files. Start test in web interface ( by default and go to ( by default it’s ) for generate new report or reset previous.

Therefore, leaving it activated while running your application in other modes is not a problem. This plugin is written for ‘test’ mode, and will silently do nothing in other modes. Overriding play.tmp because Cobertura need clean class file for works. In the /conf/nf file, enable the Cobertura module by adding this line: # The cobertura test coverage module

Enable the Cobertura module for the application It can be used to identify which parts of your Java program are lacking test coverage. This module for the Play! framework provides a plugin to support the Cobertura test coverage tool.Ĭobertura is a free Java tool that calculates the percentage of code accessed by tests.

Visual studio code java code coverage