matthewmueller / matthewmueller/component-test
browser: kill the server after it's done
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 97
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
might take some work to figure out when all the relevant requests are done. don't like CTRL + Cing all the time.
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
Start by locating the browser test server lifecycle and how requests are tracked; the issue does not name specific files or tests. The work is done when the server detects that all relevant requests are complete and exits automatically, so users no longer need to press CTRL+C.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100