Coverage metrics are not comprehensive
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 23
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Coverage collection is currently limited and should be extended.
Ideally there would be a coverage collector on each major block (TX framer, RX framer, CSRs, loopback, memory map, MAC).
In each one you want to consider three things to cover: configurations, statuses, and events. We should also cover pairs of events e.g. different events occurring under different status/config conditions.
The test suite leaves a couple gaps in the coverage already and I expect improved coverage collection will identify more.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing coverage collection in the test suite and the gaps it currently leaves. Check the TX framer, RX framer, CSRs, loopback, memory map, and MAC for coverage of configurations, statuses, events, and relevant event pairs. Done means each major block has the intended collectors and the suite reports the added coverage.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100