root
/
spring-boot
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

Merge pull request #23002 from dreis2211

Browse Source 
* pr/23002:
  Mention correct JUnit 5 annotations in Kotlin testing section

Closes gh-23002
pull/23104/head
Stephane Nicoll 4 years ago
parent 2a137a2d8a 06eb7e9777
commit 47e5db9e43
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
Unescape Escape View File

@ -7813,7 +7813,7 @@ Note that some features (such as detecting the default value or deprecated items
=== Testing === Testing
While it is possible to use JUnit 4 to test Kotlin code, JUnit 5 is provided by default and is recommended. While it is possible to use JUnit 4 to test Kotlin code, JUnit 5 is provided by default and is recommended.
JUnit 5 enables a test class to be instantiated once and reused for all of the class's tests. JUnit 5 enables a test class to be instantiated once and reused for all of the class's tests.
This makes it possible to use `@BeforeClass` and `@AfterClass` annotations on non-static methods, which is a good fit for Kotlin. This makes it possible to use `@BeforeAll` and `@AfterAll` annotations on non-static methods, which is a good fit for Kotlin.
JUnit 5 is the default and the vintage engine is provided for backward compatibility with JUnit 4. JUnit 5 is the default and the vintage engine is provided for backward compatibility with JUnit 4.
If you don't use it, exclude `org.junit.vintage:junit-vintage-engine`. If you don't use it, exclude `org.junit.vintage:junit-vintage-engine`.

Write Preview
Loading…
Cancel
Save