move to junit 5
See original GitHub issueAt the moment we have a mixture of JUnit 4 and JUnit 5 tests.
We want to completely move to JUnit 5.
For this, a new branch was introduced: [move-to-junit5]. Be aware that I removed JUnit 4 completely there, so a lot of compile errors are still there.
Sadly it is not enough to replace the imports:
- replace imports
- change assertions with messages: in junit 4 the message was the first parameter in junit 5 its the last
- change annotation names before, after, … those are renamed in junit 5
I will start from the bottom to change the stuff (now TableNamesFinderTest.java
)
To clean things up:
- remove empty generated before and after methods
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Migrating from JUnit 4 to JUnit 5 - Baeldung
In this tutorial, we'll learn how to migrate from JUnit 4 to the latest JUnit 5 release, with an overview of the differences...
Read more >Migrating from JUnit 4 to JUnit 5 | The IntelliJ IDEA Blog
The first thing we need to do in order to migrate to JUnit 5 is to add the JUnit 5 dependencies. We can...
Read more >Migrating From JUnit 4 to JUnit 5: A Definitive Guide
Key Migration Steps ; Replace testing classes and methods, Assertions and assumptions have been moved to new classes. Method argument order is ...
Read more >How to Migrate From JUnit 4 to JUnit 5 Step by Step - DZone
Open the Eclipse editor and create a simple Maven project name as JUnit 4. Please refer to the below image on how to...
Read more >Migrate to JUnit 5 from JUnit 4 - OpenRewrite
Migrate to JUnit 5 from JUnit 4 · In this tutorial, we'll use OpenRewrite to perform an automated migration from the venerable ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@manticore-projects I thought about that as well but decided against it, at least for all those simple SQL parsing tests, since you would e.g. loose the documentation, method naming, context. Or do you have something different in mind?
merge is done