iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build: add more info to SauceLabs README (#35704) 

This commit adds a debugging section to the existing
SauceLabs README. It lays out tips to debug and resolve
a few issues that I encountered while running SauceLabs
locally this morning. It also adds some clarification
to the steps in the beginning.

PR Close #35704
This commit is contained in:
Kara Erickson 2020-02-26 17:08:30 -08:00 committed by Matias Niemelä
parent b99b80c18b
commit 9a1240360b
1 changed files with 57 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
tools/saucelabs/README.md
View File

@ -2,16 +2,41 @@
## Local testing
Setup your `SAUCE_USERNAME`, `SAUCE_ACCESS_KEY` & `SAUCE_TUNNEL_IDENTIFIER` environment variables. These are required. On OSX, also set `SAUCE_CONNECT` to the path of your `sc` binary.
1. Set up your `SAUCE_USERNAME`, `SAUCE_ACCESS_KEY` & `SAUCE_TUNNEL_IDENTIFIER` environment variables.
These are required.
To run tests use:
2. On OSX and Windows, you will also need to set `SAUCE_CONNECT` to the path of your `sc` binary (Sauce Connect Proxy).
You will have to download Sauce Connect Proxy if you don't already have it downloaded.
It's available on the SauceLabs website [here](https://wiki.saucelabs.com/display/DOCS/Downloading+Sauce+Connect+Proxy).
Unzip it and point the SAUCE_CONNECT env variable to the `sc` binary.
```
export SAUCE_CONNECT=/{path_to_sc}/bin/sc
```
Note: it will not work to use the Sauce Connect that's already in node_modules unless you are using Linux.
Download the one above for other platforms.
3. Once you have your environment variables set up, run the setup task in the root of the repo:
``` bash
yarn bazel run //tools/saucelabs:sauce_service_setup
yarn bazel test //path/to:saucelabs_test_target_1 --config=saucelabs [--config=ivy]
yarn bazel test //path/to:saucelabs_test_target_2 --config=saucelabs [--config=ivy]
```
4. You can run a particular test target through SauceLabs by prefixing the target name with "saucelabs_" and adding the `--config=saucelabs` option.
For example, `packages/core/test:test_web` becomes `packages/core/test:saucelabs_test_web`.
```
yarn bazel test //path/to/target:saucelabs_target1 --config=saucelabs --config=ivy
```
Remove the `--config=ivy` if you want to run through View Engine instead.
## Additional test features
To see the test output while the tests are running (as these are long tests), add the `--test_output=streamed` option.
Note, this option will also prevent bazel from using the test cache and will force the test to run.
`bazel query` is required gather up all karma saucelabs test labels so they can be run in one command as they are tagged `manual`.
Running all ViewEngine karma tests in Saucelabs:
@ -30,11 +55,11 @@ TESTS=$(./node_modules/.bin/bazel query --output label '(kind(karma_web_test, ..
yarn bazel test --config=saucelabs --config=ivy ${TESTS}
```
To see the test output while the tests are running as these are long tests, add the `--test_output=streamed` option. Note, this option will also prevent bazel from using the test cache and will force the test to run.
## Under the hood
The `//tools/saucelabs:sauce_service_setup` target does not start the Sauce Connect proxy but it does start process which will that then listens for the start signal from the service manager script. This signal is sent by the karma wrapper script `//tools/saucelabs:karma-saucelabs` which calls `./tools/saucelabs/sauce-service.sh start`. This is necessary as the Sauce Connect Proxy process must be started outside of `bazel test` as Bazel will automatically kill any processes spwaned during a test when that tests completes, which would prevent the tunnel from being shared by multiple tests.
# Under the hood
The `//tools/saucelabs:sauce_service_setup` target does not start the Sauce Connect proxy but it does start the process that then listens for the start signal from the service manager script.
This signal is sent by the karma wrapper script `//tools/saucelabs:karma-saucelabs` which calls `./tools/saucelabs/sauce-service.sh start`.
This is necessary as the Sauce Connect Proxy process must be started outside of `bazel test` as Bazel will automatically kill any processes spawned during a test when that tests completes, which would prevent the tunnel from being shared by multiple tests.
The karma_web_test rule is to test with saucelabs with a modified `karma` attribute set to
`//tools/saucelabs:karma-saucelabs`. This runs the `/tools/saucelabs/karma-saucelabs.js` wrapper
@ -64,3 +89,27 @@ These saucelabs targets must have a few important tags:
* `manual` so they are not automatically tested with `//...`
* `exclusive` as they must be run serially in order to not over-provision Saucelabs browsers
* `saucelabs` so that they can be easily gathered up for testing in a `bazel query`
## Debugging
**Q: How do I get the tests to run on IE? I only see Chromium.**
If you see something like this at the end of your test output, it means you're not actually running SauceLabs:
```
INFO: Build completed successfully, 43 total actions
/packages/core/test:test_web_chromium
```
This is a common error caused by forgetting to prefix your test target with "saucelabs_".
For example, `/packages/core/test:test_web` becomes `/packages/core/test:saucelabs_test_web`.
**Q: How can I tell that the SauceLabs connection was successfully made?**
There is a dashboard at saucelabs.com where you can see active tunnel connections (Angular has an account).
As soon as you actually run the test target (not after the setup task), you should see an active tunnel connection under the SAUCE_TUNNEL_IDENTIFICATION_KEY you entered.
If a tunnel connection is not there, you are not actually connecting with SauceLabs.
Note: It may *look* like the tests are running because of the Bazel output.
The progress Bazel is showing does not mean that SauceLabs is connected.
If the tests are actually running, you should see the "..." test report for passing tests.