-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add note about duplicate test execution with @Suite #5080
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.
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
base: main
Are you sure you want to change the base?
Conversation
Users are surprised to see that their tests are executed twice[1]. This is the natural consequence of using a test engine to define a suite. We can at least let them know in the documentation. 1. #4327
076b9c3 to
c0a8776
Compare
documentation/src/docs/asciidoc/user-guide/advanced-topics/junit-platform-suite-engine.adoc
Outdated
Show resolved
Hide resolved
documentation/src/docs/asciidoc/user-guide/advanced-topics/junit-platform-suite-engine.adoc
Outdated
Show resolved
Hide resolved
| ===== Duplicate test execution | ||
|
|
||
| Tests in a suite are executed in addition to the tests executed by every other test | ||
| engine. This can result in the same tests being executed twice. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add sth. like the following?
Moreover, different suites may contain the same tests, potentially with different setups.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it is time to add a drawing or two. I'll come back to that. Something along the lines of:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mpkorstanje Do you have time to add the drawing for 6.0.1 or should we move this PR to 6.1.0-M1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've moved it to 6.1.0-M1. We don't have to rush this one. It's not a bug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add sth. like the following?
Done.
…uite-engine-documentation
…it-platform-suite-engine.adoc Co-authored-by: Marc Philipp <[email protected]>
| object "Jupiter Test Engine" | ||
| object "Suite Test Engine" | ||
| object "Cucumber Test Engine" | ||
| object "Spock Test Engine" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've intentionally chosen to make the diagrams sketches with concrete examples. I don't think an exact class diagram will help clarify much here.
| generateApiTables, | ||
| generateStandaloneConsoleLauncherShadowedArtifactsFile, | ||
| componentDiagram | ||
| plantUmlOutputDirectory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcphilipp I'm not sure if this is the right way to do this.
Users are surprised to see that their tests are executed twice[1]. This is the natural consequence of using a test engine to define a suite.
We can at least let them know in the documentation.
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
@APIannotations