[Enhancement]: cleanup document after removing junit4 support

Open Beginner friendly
#11,578 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

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.

Description

type/enhancement
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 ,
Dominant language
Java
Stars
8.7k
Forks
1.9k
Avg merge
2d 17h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from testcontainers/testcontainers-java

All issues in testcontainers/testcontainers-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.