Skip to content

Add README for JUnit Jupiter module documenting JUnit 5/6 support#804

Merged
rhusar merged 1 commit intoarquillian:mainfrom
rhusar:junit5-readme
Feb 18, 2026
Merged

Add README for JUnit Jupiter module documenting JUnit 5/6 support#804
rhusar merged 1 commit intoarquillian:mainfrom
rhusar:junit5-readme

Conversation

@rhusar
Copy link
Member

@rhusar rhusar commented Feb 17, 2026

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:

  • Add a README for the JUnit Jupiter (junit5) module describing JUnit 5 and JUnit 6 support, JDK requirements, and basic usage.
  • Remove the obsolete junit5 TODO.txt in favor of the new README.

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-ai
Copy link

sourcery-ai bot commented Feb 17, 2026

🧙 Sourcery has finished reviewing your pull request!


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@rhusar rhusar mentioned this pull request Feb 17, 2026
@rhusar
Copy link
Member Author

rhusar commented Feb 17, 2026

@jamezp please have a look. not optimal, but better than fending questions about this.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Member

@jamezp jamezp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @rhusar. This makes sense to me.

@jamezp
Copy link
Member

jamezp commented Feb 17, 2026

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 arquillian-junit-5-*.

@rhusar rhusar merged commit 3b3533b into arquillian:main Feb 18, 2026
12 checks passed
@rhusar
Copy link
Member Author

rhusar commented Feb 18, 2026

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 arquillian-junit-5-*.

That's a great idea, I always thought of relocation in the scope of groupIds, never artefactIds – opened #805

@rhusar rhusar deleted the junit5-readme branch February 18, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sopport for Junit 6+

2 participants

Comments