Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show line coverage on the test case itself #742

Open
4 tasks
brucetrask2 opened this issue Apr 7, 2023 · 0 comments
Open
4 tasks

Show line coverage on the test case itself #742

brucetrask2 opened this issue Apr 7, 2023 · 0 comments

Comments

@brucetrask2
Copy link

brucetrask2 commented Apr 7, 2023

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.

Screen Shot 2023-04-07 at 1 49 44 PM

Screen Shot 2023-04-07 at 12 03 20 PM

Screen Shot 2023-04-07 at 1 50 47 PM

Screen Shot 2023-04-07 at 12 02 54 PM

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant