[POC] per test code coverage using built-in Coverage.resume/suspend #124
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.
Ruby has built-in
Coverage
class to track code coverage. It is used by all major code coverage libraries in Ruby right now. This object provides a way to track total code coverage per process. There is some trick to use it for per test code coverage: useCoverage.resume
andCoverage.suspend
to start/stop coverage tracing andCoverage.results(stop: false, clear: true)
to get intermediate results.This approach is not suitable for us because of the following disadvantages:
Nevertheless, this PR explores performance of this approach to have a baseline for comparisons.
Performance evaluation
Projects used to evaluate performance:
In the following table are durations of the whole test session in seconds, in brackets overhead percentage compared to run with datadog-ci.
*
overhead here is compared to "Simplecov (total coverage)"Relevant code