databrickslabs / databrickslabs/sandbox
Measure unit test coverage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 81
- Forks
- 64
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 19
Description
Pytest drops coverage as a SQLite database. Query: select * from arc left join file on arc.file_id = file.id left join context on arc.context_id = context.id;
in go, we can either subprocess https://go.dev/doc/build-cover or parsed https://github.com/golang/go/blob/0104a31b8fbcbe52728a08867b26415d282c35d2/src/cmd/cover/html.go#L85-L100
go cover profile can also be used to build a treemap: https://github.com/golang/go/blob/0104a31b8fbcbe52728a08867b26415d282c35d2/src/cmd/cover/html.go#L85-L100
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the pytest coverage SQLite query and the linked Go build-cover and cmd/cover/html.go references. Clarify whether the goal is subprocess-based coverage, parsing, or a treemap, then define the expected output and tests before implementation. Done should mean the chosen coverage path is implemented and its results are verifiable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python, sqlite
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100