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

pitest:scmTestMutationCoverage: scmMutationCoverage but for the modified tests #456

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

sarahBuisson
Copy link

@sarahBuisson sarahBuisson commented Apr 2, 2018

It's in progress, some unit tests fails, but the principe work.

I've create a new mojo: pitest:scmTestMutationCoverage

The new mojo will do the same things than scmMutationCoverage , but only for the modified test

the consequence is, when I do
mvn pitest:scmMutationCoverage pitest:scmTestMutationCoverage -DwithHistory=true

I will have the mutation for the class who have been modified and all the test, plus the mutation for all the source but only with the modified test.
Aka, everythings we need for launching pitest on a pull-request..

I have a few question:
the issue is,
mvn pitest:scmMutationCoverage pitest:scmTestMutationCoverage -DwithHistory=true
is not a command line very easy to understand.

Can I rename the scmMutationCoverage goal into scmSourceMutationCoverage, and re-use the name "scmMutationCoverage" to do a new goal who will do all the work of "mvn pitest:scmMutationCoverage pitest:scmTestMutationCoverage -DwithHistory=true " ?

… same value of the maven project.parent.basedir
@monperrus
Copy link

Aka, everythings we need for launching pitest on a pull-request..

Awesome! Together with @bbaudry and @oscarlvp, we've been looking for that for a long time.

@hcoles
Copy link
Owner

hcoles commented Jun 26, 2018

@sarahBuisson Final had chance to look this over, sorry for the very long delay.

I can see how a goal that gives the mutation coverage of the codebase using only altered tests could be occasionally useful, but I don't follow the logic behind running it in combination with the scm mutation goal

mvn pitest:scmMutationCoverage pitest:scmTestMutationCoverage

This will not give a combined report, it will give the report of the last goal to run. I don't think the reports even could be combined as they are showing different things.

a) how well tested modified code is by the full test suite
b) how well a the subset of that test suite that has been changed tests the while codebase

I don't see how these two could be logically combined.

Am I missing something?

@sarahBuisson
Copy link
Author

@hcoles Sorry, it's an old PR I will check that.
I think I remember you need to add this " -DwithHistory=true" in order to have the two report merged.

that the point of my last paragraph : I want to merge all this goal into the same goal, but I need a comprehensible goal name for that.

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

Successfully merging this pull request may close these issues.

None yet

4 participants