Add README for JUnit Jupiter module documenting JUnit 5/6 support#804
Merged
rhusar merged 1 commit intoarquillian:mainfrom Feb 18, 2026
Merged
Add README for JUnit Jupiter module documenting JUnit 5/6 support#804rhusar merged 1 commit intoarquillian:mainfrom
rhusar merged 1 commit intoarquillian:mainfrom
Conversation
Clarifies that the junit5 module supports both JUnit 5 and JUnit 6 despite the naming convention. Resolves: arquillian#802 Signed-off-by: Radoslav Husar <radosoft@gmail.com>
|
🧙 Sourcery has finished reviewing your pull request! Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Closed
Member
Author
|
@jamezp please have a look. not optimal, but better than fending questions about this. |
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Consider adding a reference or link to this new junit5/README.adoc from the root-level README or main documentation index so users can easily discover the clarified JUnit 5/6 support information.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider adding a reference or link to this new junit5/README.adoc from the root-level README or main documentation index so users can easily discover the clarified JUnit 5/6 support information.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Member
|
Now that I think about it, and this would not block this, I wonder if it's worth moving this to junit-jupiter and doing a relocation for |
Member
Author
That's a great idea, I always thought of relocation in the scope of groupIds, never artefactIds – opened #805 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarifies that the junit5 module supports both JUnit 5 and JUnit 6 despite the naming convention. Documents JDK requirements for each JUnit version and provides basic usage example.
Resolves: #802
Summary by Sourcery
Document JUnit Jupiter module usage and replace the legacy TODO file with proper README documentation.
Documentation: