Meteor-Community-Packages / Meteor-Community-Packages/meteor-browser-tests
Prevent dev browser from running client tests when headless browser is simulaneously
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
If I'm running in TEST_WATCH mode, while developing, my client tests are running in duplicate. I'd prefer the tests to only run in nightmare/phantomjs for consistency ( and be isolated in another process). This also affects any web reporter that eventually may be installed.
I guess there are two options:
1. Have a `window` global variable set for the headless browsers, and the client tests wait for it.
2. Or use a URL with query string, and have the client check the document href. There could be unexpected interactions with routers.
Either way it seems to require changes here and in dispatch:mocha
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 tracing TEST_WATCH behavior and the dispatch:mocha entry point mentioned in the issue. Compare how client tests are launched in the development browser versus nightmare/phantomjs, including the effect on web reporters. Done means client tests run only in the headless browser and are isolated from the development browser without router-related interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100