Description of the problem or enhancement request:
I am interested in seeing code coverage on my test cases as well. It seems if I add any @ Test annotated function to a java class then it does not show line by line coverage. Just wanted to check if it were possible for me to get that information shown. The rollup numbers seem to show 100% all the time for any java file with @Test function in it.
Check the following:
[ ] If a defect or unexpected result, JMockit project members should be able to reproduce it.
For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which
can be executed without changes and reproduces the failure.
[ ] If an enhancement or new feature request, it should be justified by an example test
demonstrating the validity and usefulness of the desired enhancement or new feature.
[ ] The issue does not fall outside the scope of the project (for example, attempting to use
JMockit APIs from Groovy or Scala code, or with an Android runtime).
[ ] The JDK where the problem occurs is a final release, not a development build.
Please provide the following information:
Version of JMockit that was used:
1.49
Description of the problem or enhancement request: I am interested in seeing code coverage on my test cases as well. It seems if I add any @ Test annotated function to a java class then it does not show line by line coverage. Just wanted to check if it were possible for me to get that information shown. The rollup numbers seem to show 100% all the time for any java file with @Test function in it.
Check the following:
[ ] If a defect or unexpected result, JMockit project members should be able to reproduce it. For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which can be executed without changes and reproduces the failure.
[ ] If an enhancement or new feature request, it should be justified by an example test demonstrating the validity and usefulness of the desired enhancement or new feature.
[ ] The issue does not fall outside the scope of the project (for example, attempting to use JMockit APIs from Groovy or Scala code, or with an Android runtime).
[ ] The JDK where the problem occurs is a final release, not a development build.