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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃挕 Tip for checking coverage for the entire project #115

Open
linyutinglyt opened this issue Oct 7, 2019 · 2 comments
Open

馃挕 Tip for checking coverage for the entire project #115

linyutinglyt opened this issue Oct 7, 2019 · 2 comments

Comments

@linyutinglyt
Copy link

Hi everyone! As you may have known, the tutorial included how to measure code coverage. However, it is for class tests or methods tests. Our team (CS2103T-F13-1 @hoholyin @shiyao821 @seeziyang @Cronyxx and myself) has found a way to get code coverage for the entire project!

  1. At the top right hand corner, select the dropdown menu and choose 'Edit Configuration...'
  2. Press '+' at the top left hand corner
  3. Select 'JUnit'
  4. Name the test 'Whole project' or something you like to identify this test
  5. For Directory, choose the directory that contains all the tests of the project '.../main/src/test/'
  6. Set classpath of module to be 'main.test'
  7. For Coverage, choose 'Tracing' mode
  8. Save the changes by clicking 'Apply'

Now, when running the tests, first select 'Whole Project' from the dropdown menu, then click on 'Run with Coverage' (The icon with the green arrow and the grey shield behind)

Test coverage for the entire project will be calculated easily!

@damithc damithc changed the title Tip for checking coverage for the entire project馃挕 馃挕 Tip for checking coverage for the entire project Oct 7, 2019
@seanlowjk
Copy link

Thanks for sharing this piece of information Yu Ting!

@tcgj
Copy link

tcgj commented Oct 7, 2019

Thanks for sharing!

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

No branches or pull requests

3 participants