observablehq / observablehq/plot
Use types to determine tests coverage?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 5.4k
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
Could we create a matrix where each row would be a type/feature, and each column a unit test? This would allow us to spot which features have not enough tests, and conversely which examples to use to document a given feature.
By "feature" I'm not only talking about, say, "support for curve", but more detailed "support for named curves + support for curve functions", each type being a unique subfeature.
I suppose there already exists tools that leverage types to do this?
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
No files, tests, or entry points are named. Start by reviewing how types, features, and unit tests are currently represented, then determine whether a coverage matrix or an existing type-based tool fits. Done would require an agreed design and an implemented way to identify under-tested features and relevant documentation examples.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100