Add test coverage for react_types utils
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 432
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Putting this off till later...
Test is on branch link-2020/react_types_test
My test passes by adding the local file hack to the utility method I have in the test file, but not when I try and add the hack to parseAndGetResolvedUnits function and use that instead
The file should get well covered by integration tests anyway, but we may want to revisit in the future
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 reviewing the test on branch link-2020/react_types_test and the parseAndGetResolvedUnits function. Compare the local file hack used by the test with the utility implementation, then check the existing integration-test coverage. Done means the react_types utilities have meaningful passing coverage without relying on the local file hack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100