-
Notifications
You must be signed in to change notification settings - Fork 292
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
Per test code coverage in CI Visibility #5146
Per test code coverage in CI Visibility #5146
Conversation
BenchmarksParameters
See matching parameters
SummaryFound 0 performance improvements and 1 performance regressions! Performance is the same for 21 cases.
|
dd9e287
to
fad217b
Compare
cdfa5f9
to
b5d7d55
Compare
b5d7d55
to
1371a67
Compare
1371a67
to
7330034
Compare
} | ||
|
||
@Override | ||
public boolean equals(Object obj) { |
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.
Is this equals
implementation really needed?
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.
Good catch, that was a leftover from some experiments, removed
Co-authored-by: Santiago M. Mola <santiago.mola@datadoghq.com>
ff4a9dc
to
2300346
Compare
What Does This Do
Adds per-test code coverage support for CI Visibility product: code coverage info is collected separately for every test case.
Motivation
Per-test code coverage data is needed to support CI Visibility Intelligent Test Runner.
Additional Notes
Code coverage is implemented on top of Jacoco, by instrumenting Jacoco classes and injecting bytecode that inserts additional test probes.