Recent changes to feature-requests

#86 Merge task fails if one input file is corrupted

Marc R. Hoffmann — Mon, 27 May 2013 08:45:19 -0000

status: open --> closed-fixed
Group: --> Eclipse3.3

#87 Hit Counter

Marc R. Hoffmann — Mon, 27 May 2013 08:44:08 -0000

status: pending --> closed-wont-fix

Cover a single test from JUnit view

Ryan Gustafson — Thu, 09 Aug 2012 22:32:17 -0000

When I'm writing a single @Test method, I'll often run the entire TestClass, and right click a test in the JUnit view, and run just that one test, and rerun until it works as desired. Even if I ran the TestClass originally using coverage, the single test run does not get covered. It would be great if I could run coverage for just that test (preferably sticky based upon original TestClass run).

This would offer great insight into what precisely that one test is hitting. Is the test doing what I think it is doing?

Hit Counter

Anonymous — Mon, 30 Jul 2012 13:57:56 -0000

I would love to see the number of hits per line executed. For example a statement in a for loop is executed 10 times but an unreachable statement is executed 0 times. It is displayed on the side parallel to the line numbers.

This can be found in commercial alternatives such as Clover and in other open source code coverage tools such as Gcov.

Hit Counter

Anonymous — Mon, 30 Jul 2012 13:57:56 -0000

Ticket 87 has been modified: Hit Counter
Edited By: Marc R. Hoffmann (mtnminds)
Status updated: u'pending' => u'closed-wont-fix'

Merge task fails if one input file is corrupted

Ivan — Mon, 09 Jul 2012 14:17:18 -0000

I have a lot of coverage result files that come from many different sources (Junit, testNG, other)
So when I want to generate a report, a merge all the files into one with this ant call:

But some files can be corrupted (the test crashed or even isn't finished yet.
And then the whole task fails:
15:07:25 /tmp/jenkins_slave/workspace/DAILY_TESTS_ENDER/BuildUtil/advanced-tasks.xml:168: Unable to read /tmp/jenkins_slave/workspace/DAILY_TESTS_ENDER/jacoco.1340966180.ec

I would like to be able to say to the "merge" task that it should ignore corrupted/illegal/abnormal files instead of stopping.
IE:
Log a warning in MergeTask#loadSourceFiles() at line 116 instead of raising an exception.

Merge task fails if one input file is corrupted

Ivan — Mon, 09 Jul 2012 14:17:18 -0000

Ticket 86 has been modified: Merge task fails if one input file is corrupted
Edited By: Marc R. Hoffmann (mtnminds)
Status updated: u'open' => u'closed-fixed'
_milestone updated: '' => u'Eclipse3.3'

JaCoCO Maven: exec file parameter naming

Anonymous — Mon, 02 Jul 2012 18:51:53 -0000

I have observed that the report goal and the prepare-agent goal have different names for the destFile.
The prepare-agent uses the name destFile whereas the report goal uses dataFile. It would be nice to use the same name which would make life easier.

Made possible to aggregate Report

Anonymous — Wed, 20 Jun 2012 12:32:18 -0000

Sometimes when using maven I wanna see the coverage result for the whole project and not just for single modules.

The attached patch introduces a new configuration aggregate. When true, maven will collect jacoco.exec from each module and combine then all in order to create A report for the entire project.

get Maven plugin report task configurable with command-line

Anonymous — Thu, 14 Jun 2012 15:40:43 -0000

In order to be able to be able to generate reports in a non-intrusive way in build process, it would be useful to provide ability to invoke and configure the "report" task from command-line.
It's basically about adding "expressions" annotations to the Mojo.