-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Provide a JUnit 5 Extension instead of a JUnit 4 Rule #2371
Comments
Related: android/android-test#224 |
igordmn
added a commit
that referenced
this issue
Aug 17, 2023
For iOS/Web it will be stabilized with stabilizing these targets themselves. Also, we should expose uiTest for them, not uiTestJUnit4 JUnit5 support will be provided in the future in [this issue](#2371) ## API Changes - Testing framework is stabilized for Desktop - `compose.uiTestJUnit4` is renamed to `compose.desktop.uiTestJUnit4`
This was referenced Aug 17, 2023
igordmn
added a commit
that referenced
this issue
Aug 17, 2023
For iOS/Web it will be stabilized with stabilizing these targets themselves. Also, we should expose uiTest for them, not uiTestJUnit4 JUnit5 support will be provided in the future in [this issue](#2371) ## API Changes - Testing framework is stabilized for Desktop - `compose.uiTestJUnit4` is renamed to `compose.desktop.uiTestJUnit4`
igordmn
added a commit
that referenced
this issue
Aug 17, 2023
For iOS/Web it will be stabilized with stabilizing these targets themselves. Also, we should expose uiTest for them, not uiTestJUnit4 JUnit5 support will be provided in the future in [this issue](#2371) ## API Changes - Testing framework is stabilized for Desktop - `compose.uiTestJUnit4` is renamed to `compose.desktop.uiTestJUnit4`
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Since the test API is considered experimental anyway, and given that JUnit 4 has been outdated for some time now, it would be nice if the current
TestRule
were replaced by aExtension
.I already took a shot at writing such a thing in my own code, but the structure of the current
TestRule
makes it impossible to reuse - it's implemented by wrapping around the test execution, which is the one kind of extension which JUnit 5 doesn't have support for.I also attempted to pull the code out of the current test rule to write a new extension, but it's relying on a lot of internal classes, so I think I'd have to clone the entire module to get anything working.
The text was updated successfully, but these errors were encountered: