-
Notifications
You must be signed in to change notification settings - Fork 72
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
Setting the Environment Variables with version 1.18.0 not working with Junit 5 #70
Comments
Does this work with System Rules 1.17.2 and JUnit Lambda (JUnit 5)? |
Yes it works with System Rules 1.17.2 and Junit 5. |
Same problem here, 1.80.0 and 1.19.0 doesn't work but 1.17.2 does. |
Same for me, 1.17.2 works but 1.19.0 doesn't for JUnit 5.3.2 |
The same for me - 1.17.2 works but 1.18.0 and 1.19.0 does not for JUnit 5.5.0 |
Using 1.17.2 works but throws
Is there any solution currently in progress to avoid this error? |
Also working with 1.17.2 (with the above warnings) when using JUnit 5. 1.19 does not work in the sense that environmental variables are still NULL after being set. |
Jupiter support available in https://github.com/webcompere/system-stubs/tree/master/system-stubs-jupiter - a fork of |
Any chance this is getting fixed for? Java 17 (Temurin) and junit 4, using 1.17.2:
Java 17 (Temurin) and junit 4, using 1.19.0:
|
System Stubs is essentially compatible with System Rules (package names have changed) and does support later Java. |
@ashleyfrieze Thanks, good to know! |
It wasn't my intention to replace this tooling. I wanted a JUnit 5 plugin that worked a certain way. I've also offered the JDK17 compatible solution to whoever wants to steal the code from my repo. That said, it comes at a price, which is the adoption of |
I am trying to set the environment variables using the version 1.18.0 and I am always getting null. I am using Junit 5 and have no issues using 1.17.2 version to set the system environment variables. I need to set different environment values for different tests, so not setting the value right after creating the rule. My code looks like the following:
The text was updated successfully, but these errors were encountered: