-
Notifications
You must be signed in to change notification settings - Fork 273
Migrate from JUnit4 to JUnit5 #756
Copy link
Copy link
Closed
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.
Description
The library uses JUnit4 . JUnit5 is stable. Is it worth migrating? I can do it. It's interesting for me.
It can be something like that:
- update maven-surfire-plugin (if necessary)
- update junit version
- run old tests with vintage junit runner
- refactor old tests step by step
Progress:
- [chore: migration tests in credentials module from JUnit4 to JUnit5 (#756) #761]
- [Migration tests in appengine module from JUnit4 to JUnit5 (#756) #760]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - first iteration (#756) #762 ]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - second iteration (#756) #763]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - third iteration (#756) #764]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - fourth iteration (#756) #766]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - fifth iteration (#756) #767]
- [chore: migrate tests in oauth2_http module from JUnit4 to JUnit5 - sixth iteration (#756) #769]
- UPDATE(10/21/2021 by @chanseokoh): [build: fix integration test #775]
Kind regards
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.