Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support connection to remote browser
See original GitHub issueIt is a proposal.
Current behavior:
Currently, all browsers for Cypress runner should be installed on the same host (or same container). It makes it hard to have custom setups in complex projects with a lot of services connected via Docker.
Desired behavior:
Support possibility to connect to remote Chrome browser via WS, running locally or in the container.
For example, when using e2e testing with Jest + Puppeteer setup, I can use a separate Chrome container and just set a remote chrome address in config.
connect: {
browserURL: 'http://127.0.0.1:9222'
}
Steps to reproduce: (app code and test code)
There is no such option yet.
Versions
Cypress 3.8.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:49
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m very interested in using this feature! Is there a design document for the feature? Anyway I can help to implement it?
Are there any news on this one?