Adds description for JUnit 5 usage #911
Conversation
docs/usage.md
Outdated
|
|
||
| ### JUnit 5 | ||
|
|
||
| **JUnit5**: you need to manually start container in *@BeforeAll* annotated method in test (tear down happens automatically on test end) |
There was a problem hiding this comment.
this example does not reflect the previous one, with JUnit 4. Maybe we should replace it with @BeforeEach/@AfterEach
There was a problem hiding this comment.
Or alternatively, use @ClassRule in the JUnit4 example.
There was a problem hiding this comment.
Also please uppercase You and . at the end of the sentence.
You need to manually start the container in a *@BeforeAll* annotated method in your test
There was a problem hiding this comment.
Also the tear down happen on JVM exit.
There was a problem hiding this comment.
Agree, will adjust it
docs/usage.md
Outdated
|
|
||
| ### Junit 4 | ||
|
|
||
| **JUnit4 @Rule/@ClassRule**: this mode starts container before your tests and tears it down afterwards. |
There was a problem hiding this comment.
That part was copied from database_container.md - should I also adjust it there too ?
docs/usage.md
Outdated
|
|
||
| **JUnit5**: you need to manually start container in *@BeforeAll* annotated method in test (tear down happens automatically on test end) | ||
|
|
||
| Start container in @BeforeAll method: |
There was a problem hiding this comment.
Start container in a method annotated with @BeforeAll:
docs/usage.md
Outdated
|
|
||
| ### JUnit 5 | ||
|
|
||
| **JUnit5**: you need to manually start container in *@BeforeAll* annotated method in test (tear down happens automatically on test end) |
There was a problem hiding this comment.
Or alternatively, use @ClassRule in the JUnit4 example.
docs/usage.md
Outdated
|
|
||
| ### JUnit 5 | ||
|
|
||
| **JUnit5**: you need to manually start container in *@BeforeAll* annotated method in test (tear down happens automatically on test end) |
There was a problem hiding this comment.
Also please uppercase You and . at the end of the sentence.
You need to manually start the container in a *@BeforeAll* annotated method in your test
docs/usage.md
Outdated
|
|
||
| ### JUnit 5 | ||
|
|
||
| **JUnit5**: you need to manually start container in *@BeforeAll* annotated method in test (tear down happens automatically on test end) |
There was a problem hiding this comment.
Also the tear down happen on JVM exit.
|
@artjomka Thanks for your contribution. |
Adds separate section in usage documentation to address differences in JUnit4/JUnit5 approaches.