#1659 confirmed
Timo Sillanpää

Cobertura module outdated (documentation and Java 1.7 support)

Reported by Timo Sillanpää | April 2nd, 2013 @ 07:06 AM | in 1.4.x

The Play tutorial at http://www.playframework.com/documentation/1.2.5/guide10#cobertura shows how to install the Cobertura module for measuring code coverage. Unfortunately the instructions are outdated as they tell you to specify the following in application.conf:

# Import the cobertura module in test mode
%test.module.cobertura=${play.path}/modules/cobertura

There are two problems with the above:
1. The application fails to start, giving you the message "Oops, module not found: /usr/local/play-1.2.5/modules/cobertura". The problem can be fixed by adding a "-2.4" suffix, resulting in "%test.module.cobertura=${play.path}/modules/cobertura-2.4".
2. After fixing the application.conf line, Play gives the following warning:

"Declaring modules in application.conf is deprecated. Use dependencies.yml instead (module.cobertura)"

When the above cobertura line is removed from application.conf, "play auto-test" does not complain anything but "play test" gives you a bunch of errors at application shutdown, complaining on every occurrence of the Java 7 diamond operator:

09:52:21,898 WARN  ~ JavaNCSS got an error while parsing the java file /Users/xxxx/path/to/file/xyz/ReferralService.java
ParseException in STDIN
Last useful checkpoint: "xyz/ReferralService.fetchNewAndModified()"
Encountered ">" at line 75, column 50.
Was expecting one of:
    "boolean" ...
    "byte" ...
    "char" ...
    "double" ...
    "float" ...
    "int" ...
    "long" ...
    "short" ...
    <IDENTIFIER> ...
    "?" ...

and

09:52:22,235 INFO  ~ Data file does not contain instrumentation information for the file xyz/ReferralService.java.  Ensure this class was instrumented, and this data file contains the instrumentation information.

Obviously "play auto-test" just silently ignores the same errors. So it is a bit unclear whether the coverage results are correct.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Tags

Pages