Test Indexes and Reporters #616
Draft
Conversation
This file contains 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.
@slawekjaranowski This is a work in progress.
The test reporters must not determine the test status upon timings of test events.
The test reporters must not identify the test run upon text literals (e.g. class and method) of the test entry.
These are all the causes why parallel tests are chaotic in JUnit5 report.
These are the causes why JUnit5 and JUnit4 parameterized tests give different reports.
These are the causes why Cucumber is not able to work with dynamic tests.
Nevertheless this would fix the issue with memory consumption in JUnit47 parallel test and the provider.
So I have some doubts about #516 #544 and #608 and I will make the audit there as well.