| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
We periodically send coverage reports for the regressions detection.
|
| |
|
|
| |
The last filtering step is the empty dirs removal.
|
| |
|
|
| |
Tree view now shows the total drop for every item.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
cover.Format controls the resulting view.
It allows to:
1. Remove records with 0 covered blocks.
2. Remove lines with low (user defined) coverage.
3. Order records by the covered lines drop value.
The corresponding GET parameters are:
1. Implicitly enabled for onlyUnique records.
2. min-cover-lines-drop=%d
3. order-by-cover-lines-drop=1
|
| | |
|
| |
|
|
| |
It will simplify the json API links.
|
| | |
|
| |
|
|
|
|
|
|
| |
1. Init coveragedb client once and propagate it through context to enable mocking.
2. Always init coverage handlers. It simplifies testing.
3. Read webGit and coveragedb client from ctx to make it mockable.
4. Use int for file line number and int64 for merged coverage.
5. Add tests.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1. Make heatmap testable, move out the spanner client instantiation.
2. Generate spannerdb.ReadOnlyTransaction mocks.
3. Generate spannerdb.RowIterator mocks.
4. Generate spannerdb.Row mocks.
5. Prepare spannerdb fixture.
6. Fixed html control name + value.
7. Added multiple tests.
8. Show line coverage from selected manager.
9. Propagate coverage url params to file coverage url.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Hover mouse onto the percent value to see details.
To test:
$ go run ./tools/syz-cover -heatmap upstream -from 2024-08-23 -to 2024-08-23
$ google-chrome upstream.html
|
| | |
|
| | |
|
| |
|