You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+42-3Lines changed: 42 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -185,6 +185,22 @@ Run frontend tests:
185
185
186
186
### Integration Tests
187
187
188
+
#### Cypress
189
+
190
+
Cypress integration tests are run via [Cypress.io](https://www.cypress.io/).
191
+
192
+
Launch Cypress test runner:
193
+
```
194
+
cd frontend
195
+
oc login ...
196
+
yarn run test-cypress
197
+
```
198
+
199
+
This will launch the Cypress test runner where you can run one or all cypress tests.
200
+
201
+
[**_More information on Console's Cypress usage_**](frontend/packages/integration-tests-cypress/README.md)
202
+
#### Protractor
203
+
188
204
Integration tests are run in a headless browser driven by [protractor](http://www.protractortest.org/#/).
189
205
Requirements include Chrome or Firefox, a working cluster, kubectl, and bridge itself (see building above).
190
206
By default, it will look for Chrome in the system and use it, but if you want to use Firefox instead, set `BRIDGE_E2E_BROWSER_NAME` environment variable in your shell with the value `firefox`.
@@ -220,7 +236,6 @@ For macOS, you can use:
220
236
```
221
237
yarn run webdriver-update-macos
222
238
```
223
-
224
239
#### How the Integration Tests Run in CI
225
240
226
241
The end-to-end tests run against pull requests using [ci-operator](https://github.com/openshift/ci-operator/).
@@ -245,7 +260,7 @@ If you don't want to run the entire e2e tests, you can use a different suite fro
245
260
$ ./test-gui.sh <suite>
246
261
```
247
262
248
-
#### Hacking Integration Tests
263
+
#####Hacking Protractor Tests
249
264
250
265
To see what the tests are actually doing, it is posible to run in none `headless` mode by setting the `NO_HEADLESS` environment variable:
251
266
@@ -265,7 +280,7 @@ To avoid skipping remaining portion of tests upon encountering the first failure
7. Pauses browser when not using `--headless` argument!
277
292
293
+
#### How the Integration Tests Run in CI
294
+
295
+
The end-to-end tests run against pull requests using [ci-operator](https://github.com/openshift/ci-operator/).
296
+
The tests are defined in [this manifest](https://github.com/openshift/release/blob/master/ci-operator/jobs/openshift/console/openshift-console-master-presubmits.yaml)
297
+
in the [openshift/release](https://github.com/openshift/release) repo and were generated with [ci-operator-prowgen](https://github.com/openshift/ci-operator-prowgen).
298
+
299
+
CI runs the [test-prow-e2e.sh](test-prow-e2e.sh) script, which runs the cypress tests and the protractor `e2e` test suite defined in [protractor.conf.ts](frontend/integration-tests/protractor.conf.ts).
300
+
301
+
You can simulate an e2e run against an existing 4.0 cluster with the following commands (replace `/path/to/install-dir` with your OpenShift 4.0 install directory):
If you don't want to run the entire e2e tests, you can use a different suite from [protractor.conf.ts](frontend/integration-tests/protractor.conf.ts). For instance,
312
+
313
+
```
314
+
$ ./test-gui.sh <suite>
315
+
```
316
+
278
317
### Deploying a Custom Image to an OpenShift Cluster
279
318
280
319
Once you have made changes locally, these instructions will allow you to push
0 commit comments