Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use @Nested classes instead of comments for grouping tests #2951

Open
bvkatwijk opened this issue Dec 29, 2024 · 3 comments · May be fixed by #2960
Open

Use @Nested classes instead of comments for grouping tests #2951

bvkatwijk opened this issue Dec 29, 2024 · 3 comments · May be fixed by #2960
Assignees
@bvkatwijk

Comments

@bvkatwijk
Copy link
Contributor

JUnit Jupiter, tests can be grouped using Nested classes

@nested tests give the test writer more capabilities to express the relationship among several groups of tests. Such nested tests make use of Java’s nested classes and facilitate hierarchical thinking about the test structure

This seems to fit the exact purpose of the -- comment divisors in test., and enables a number of useful features like being able to run the set of nested tests individually.
@bvkatwijk bvkatwijk mentioned this issue Dec 29, 2024
Closed
@bvkatwijk
Copy link
Contributor Author

I have some time to contribute to open source projects - let me know if this is something I could pick up 👍

@pivovarit
Copy link
Member

pivovarit commented Dec 30, 2024 •
edited
Loading

Sure thing :) just please target version/0.x first

@pivovarit
Copy link
Member

A quick heads up: https://github.com/orgs/vavr-io/discussions/2953

version/0.x will be becoming the new main branch - no worries, I will backport your changes

@bvkatwijk bvkatwijk linked a pull request Jan 3, 2025 that will close this issue
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bvkatwijk bvkatwijk

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use JUnit @Nested classes for tests instead of comment sections bvkatwijk/vavr
2 participants
@pivovarit @bvkatwijk