redhat-developer / redhat-developer/rhdh-plugins
Improve scorecard code-coverage module
Open
Nobody has claimed this yet.
enhancement
feature
Tests
triaged
workspace/scorecard
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 120
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 337
Description
This is a follow-up on #3474 and #3476 and should address 5 left overs:
- Add or verify backend-to-backend authentication
- Add to the module README.md how to import data with some curl examples
- Add some demo data to the project (examples/code-coverage folder) that can be importet with one command, prepare app-config.yaml if some secrets are required to import data for example with curl.
- Add playwright / e2e tests to for the module that ensures that all metrics are available (independ of the values are good or bad)
- Check if its possible to import the demo data automatically in playwright.
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 reading follow-ups #3474 and #3476, then inspect the code-coverage module's README.md, examples/code-coverage, app-config.yaml, and the Playwright test entry points. Done means authentication is covered, curl import instructions and runnable demo data are available, and end-to-end tests verify every metric and assess automatic demo-data import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- documentation, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100