IQSS / IQSS/dataverse-frontend
Coveralls: code coverage can change unexpectedly
Open
Nobody has claimed this yet.
GREI Re-arch
SPA.Q2
tests
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Analyze what is happening to cause our code coverage to go change unexpectedly. Possible cause: using randomized faker data that may change the branches in the code that are being executed.
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 comparing the Coveralls results from repeated runs and trace where randomized Faker data is used in the TypeScript test suite. Re-run coverage with the same and different generated data to determine whether branch execution changes. Done means the source of the variability is identified and coverage is reproducible or the required follow-up is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100