[DERBY-5512] emma-single and emma-all don't use the instrumented jars

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: Build tools, Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 23/Nov/11 16:57
• Updated: 24/Nov/11 08:59
• Resolved: 24/Nov/11 08:59

Description

When running the Ant targets that produce code coverage reports for the JUnit tests, the reports are empty:

$ ant -Dderby.junit.testclass=org.apache.derbyTesting.functionTests.tests.lang.CommentTest emma-single 2>&1
(...)
emma-report:
[report] [EMMA v2.0, build 5312 (2005/06/12 19:32:43)]
[report] input data path:
[report]

{ [report] /code/derby/trunk/junit_20111123_1751/coverage.em [report] }

[report] source path:
[report]

{ [report] /code/derby/trunk/java/client [report] /code/derby/trunk/java/demo [report] /code/derby/trunk/java/drda [report] /code/derby/trunk/java/engine [report] /code/derby/trunk/java/shared [report] /code/derby/trunk/java/storeless [report] /code/derby/trunk/java/tools [report] }

[report] processing input file [/code/derby/trunk/junit_20111123_1751/coverage.em] ...
[report] loaded 1542 metadata entries
[report] 1 file(s) read and merged in 194 ms
[report] nothing to do: no runtime coverage data found in any of the data files
(...)

Running Ant with the -v option revealed that the JUnit test was run with the uninstrumented jar files. I suspect that this is because DERBY-4089 made the build script set derby.junit.classpath automatically if it's not already set. Since Ant properties cannot be changed once they've been assigned a value, this prevents the emma-instrumentation target from building a derby.junit.classpath that points to the instrumented jars.

Issue Links

• is broken by: DERBY-4089 It should be possible to run unit tests right after "ant all"