-
Notifications
You must be signed in to change notification settings - Fork 348
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
Allow reusing surefire environmentVariables for pitest #1317
Comments
Hi @MosheElisha, Thanks for the suggestion. This ought to be straight forward, I'll look to include it in the next release. |
This in now implemented in #1319. The behavior is always on, which I shouldn't imagine would cause an issue. If different values are needed when running via pitest, the ones from surefire can be overwritten in the pitest config. |
Wow! Perfect! Thanks a lot, @hcoles ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My code requires quite a lot of environment variables to run properly.
They are configured in the maven-surefire-plugin > configuration > environmentVariables so the unit tests will pass.
The code (and tests) will fail without these environmentVariables (it actually took me a long time to understand that this is the reason why I don't see mutation coverage).
Currently, I need to repeat the environmentVariables I defined in maven-surefire-plugin configuration also in pitest-maven configuration.
Would be great if there can be a way to use the surefire environmentVariables for pitest-maven so they will be defined only once.
Something like
mergeSurefireEnvironmentVariables=true
.Current workaround is to place the env var value in a property so at least the value can be shared.
The text was updated successfully, but these errors were encountered: