Replies: 1 comment
-
|
The reason is that the In other words, we cannot introduce a In addition, we assumed people would not need access to all configuration parameters within a Jupiter extension. Normally, an extension knows the names of the configuration properties it needs to look up. Why do you need to access all configuration parameters from a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The
org.junit.jupiter.api.extension.ExtensionContexthas a methodgetConfigurationParameter(...), but why it hasn'tgetConfigurationParameters()?The only way to get configuration parameters I've found is to implement
org.junit.platform.launcher.TestExecutionListenerBeta Was this translation helpful? Give feedback.
All reactions