You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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: