Parameterised tests are really powerful and can also reduce duplicating tests to give different inputs, the parameters can even be provided through a variety of mechanisms. Nested tests allow us to put our tests into groups, increasing readability and allowing us to reduce repetition within test names. We don’t need to worry about having to update all of our tests in one go, as we can use the vintage engine to run these and have both JUnit 4 and 5 tests within our project.Īs users of the testing framework, it’s likely that the most interesting part is the new features we get access to. JUnit Vintage gives us an engine for running our previous JUnit 4 tests.JUnit Jupiter defines how we write JUnit 5 tests and then contains an engine for running these tests on the platform.JUnit Platform is the underlying layer on which testing frameworks can run on the JVM and offers up the API for different test engines.The architecture of JUnit 5 is quite a significant change from before, with the framework being split into three major components. In the case of JUnit 5, with some changes to your Gradle dependencies, you can use it right now from your Java and Kotlin unit tests. Often Android developers are used to waiting a while for new things from the Java-world to be an option on Android.
From a user-perspective it offers a number of useful new features and various other benefits. JUnit 5 is the next generation of JUnit testing and has quite a new structure.
JUnit 4 has always been the standard unit testing framework for Android development, however, a production version of JUnit 5 has been available for quite a while.
0 kommentar(er)
