[Core] Significantly reduce the size of the html report #2172
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
Codecov Report
@@ Coverage Diff @@
## main #2172 +/- ##
=========================================
Coverage 82.79% 82.79%
- Complexity 2321 2324 +3
=========================================
Files 306 306
Lines 8292 8294 +2
Branches 762 762
=========================================
+ Hits 6865 6867 +2
Misses 1118 1118
Partials 309 309
Continue to review full report at Codecov.
|
Cucumber-JVM will emit all step, hook and parameter type definition for each scenario. This results in a deluge of messages that effectively grows with the square of the number of scenarios (more scenarios, result in more step definitions). Executing some 500 scenarios can result in a html report anywhere between 150 and 300 MiB. The step, hook, and parameter type definitions are not used by the html report and can be filtered out. This reduces the report size to some 15 MiB. While still large this is much more manageable. Further reductions will have to come from: 1. Improvements to `cucumber/react` 2. Fixing Cucumber JVM to only define steps, hooks and parameter types once.
mpkorstanje
force-pushed
the
cucumber/1232
branch
from
0d4654e to
f328000
Compare
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.
Cucumber-JVM will emit all step, hook and parameter type definition for each
scenario. This results in a deluge of messages that effectively grows with
the square of the number of scenarios (more scenarios, result in more step
definitions).
Executing some 500 scenarios can result in a html report anywhere between
150 and 300 MiB. The step, hook, and parameter type definitions are not used
by the html report and can be filtered out. This reduces the report size to
some 15 MiB. While still large this is much more manageable.
Further reductions will have to come from:
cucumber/reactSee: https://github.com/cucumber/cucumber/issues/1232https://github.com/cucumber/cucumber/issues/1232