matthewmueller / matthewmueller/component-test
code coverage?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 97
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
thoughts on implementing code coverage reporting using yields/coverage?
cli api could resemble:
$ component test {browser,phantom} --coverage
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
No files or tests are named. Start by reviewing the component test CLI and the proposed yields/coverage integration, then define how component test {browser,phantom} --coverage should report results; done means the command produces code coverage reporting for the supported test targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100