Allow faking a tty for tests that need it
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 605
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
Either for all modules as a global option, or one a module-by-module basis as part of their config in lookup.json.
Using something like https://github.com/chjj/pty.js
This is to help stop issues like https://github.com/nodejs/node/issues/8138 before they're released.
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 how module configuration is represented in lookup.json and how tests are launched. Compare the global-option and per-module approaches, and review pty.js as the proposed mechanism; done means tty-dependent tests can be exercised without causing release regressions like the linked Node.js issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100