Fix Connection to SauceLabs via SauceConnect
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
As documented in `TEST.md`, running Sauce Connect (a proxy server that opens a secure tunnel between SauceLabs and a local Linkerd dashboard instance) in conjunction with `bin/web integration cloud` is supposed to launch cross-browser tests via SauceLabs. Currently, running this command fails to launch the tests. Running the browser tests on my local machine does work as expected.
Note: `bin/web integration local`, which runs browser tests on your local machine, has been updated in PR #3646.
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 with TEST.md and the bin/web integration cloud entry point; reproduce the SauceConnect failure and compare it with bin/web integration local, including the changes referenced in PR #3646. Done means the cloud command launches the cross-browser SauceLabs tests through the secure tunnel while local browser tests continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100