Migration guides

• Migration from v1 to v2
• Migration to JUnit5

Migration from v1 to v2

Migration from v1 to v2 staying with JUnit4

• Replace test dependency com.tngtech.java:junit-dataprovider with com.tngtech.junit.dataprovider:junit4-dataprovider
• API is kept same but largely forwards calls to new core API

Migration from v1 to v2 and from JUnit4 to JUnit Jupiter

• See detailed migration information

Migration from v1 to v2 and from JUnit4 to JUnit Jupiter Parameterized Tests

• See detailed migration information

Migration to JUnit5

There are three different approaches for using JUnit dataprovider with JUnit5:

Migration to JUnit Jupiter

• Requires JUnit dataprovider v2.0
• Based on JUnit Jupiters @TestTemplate
• Full JUnit4 dataprovider replacement containing all features based on JUnit Jupiters engine
• Moderate migration path
• Supporting meta-annotations very well to provide custom, composed annotations
• For more details, see below)
• See detailed migration information

Migration to JUnit Jupiter Parameterized Tests

• Requires JUnit dataprovider v2.0
• Based on JUnit Jupiters @ParameterizedTest
• JUnit4 dataprovider replacement based on JUnit Jupiter Parameterized Tests (= JUnit Jupiters "dataprovider" approach)
• Moderate migration effort
• JUnit Jupiter Parameterized Tests already contains the basic features of JUnit dataprovider natively (even if they are implemented differently)
• For more details, see below)
• See detailed migration information

JUnit5 Dataprovider Extension (external library)

Another possibility to use JUnit5 is using the external library JUnit5 Dataprovider Extension. It is a lightweight approach with minimalistic migration effort introduced by aburmeis, see junit5-dataprovider-extension. But it still requires JUnit4 on the classpath.