testcontainers / testcontainers/testcontainers-java
[Enhancement]: cleanup document after removing junit4 support
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
Core
Proposal
cleanup junit limitation for document
details
https://java.testcontainers.org/test_framework_integration/junit_5/
According to the documentation, it still says that a JUnit 4 dependency is required.
Since this module has a dependency onto JUnit Jupiter and on Testcontainers core, which has a dependency onto JUnit 4.x, projects using this module will end up with both, JUnit Jupiter and JUnit 4.x in the test classpath.
However, these changes should have completely removed the dependency on JUnit 4.
- since #970
- and #10805 ,
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the JUnit 5 documentation at java.testcontainers.org/test_framework_integration/junit_5/ and compare its JUnit 4 dependency statement with the changes referenced in #970 and #10805. Done means the documentation no longer claims that a JUnit 4 dependency is required if those changes removed it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100