IQSS / IQSS/dataverse-client-javascript
Add coverage run github action step
Open
Nobody has claimed this yet.
GREI Re-arch
Original size: 3
Size: 3
SPA.Q4.10
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 11
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
Overview of the feature request
Just as we run tests to be able to deploy the package in GitHub Package Registry, we need to verify that test coverage remains within acceptable limits. The goal is to create the github action / step responsible for this.
What inspired the request?
Frontend standup discussion
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to js-dataverse?
None
Any open or closed issues related to this feature request?
None
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 inspecting the repository's existing GitHub Actions workflow for the test and GitHub Package Registry deployment steps. Determine how coverage is currently produced and what limit should be enforced; done means the workflow runs coverage and verifies it remains within the accepted range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100