matthewmueller / matthewmueller/component-test
make sure we have a reasonable error when phantomjs isn't installed
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 97
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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
The issue names no files, tests, or entry points. Start by locating the PhantomJS launch path in the component test runner; done means an understandable error is shown when PhantomJS is unavailable, with a test covering that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100