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: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -396,6 +396,7 @@ By default, top level tasks will execute for all packages. However, most scripts
396
396
|`test-unit`| Run unit tests |
397
397
|`test-integration`| Run integration tests |
398
398
|`test-e2e`| Run end-to-end tests |
399
+
|`test-system`| Run system tests |
399
400
|`test-watch`| Run unit tests and rebuild/rerun on file changes |
400
401
401
402
> Most of the time you will only want to run a task within a specific package; this can be done by providing the package name as a scope to the top level task.
@@ -428,7 +429,6 @@ Each package is responsible for building itself and testing itself and can do so
428
429
|`test`| Runs all tests once (this usually means running unit tests; via `yarn test-unit`) |
429
430
|`test-unit`| Run all unit tests within the package;`exit 0`if N/A |
430
431
|`test-integration`| Run all integration tests within the package;`exit 0`if N/A |
431
-
|`test-e2e`| Run all e2e tests within the package;`exit 0`if N/A |
432
432
|`test-watch`| Run all unit tests in the package in watch mode |
433
433
434
434
#### Debugging
@@ -486,11 +486,11 @@ This is to ensure that links do not go dead in older versions of Cypress when th
486
486
487
487
For most packages there are typically unit and integration tests.
488
488
489
-
Our true e2e tests are in [`packages/server`](packages/server), which test the full stack all together.
489
+
Please refer to each packages' `README.md` which documents how to run tests. It is not feasible to try to run all of the tests together. We run our entire test fleet across over a dozen containers in CI.
490
490
491
-
Additionally, we test the code by running it against various other example projects in CI. See CI badges and links at the top of this document.
491
+
There are also a set of system tests in [`system-tests`](system-tests) which attempt to test the entire Cypress App as close to real world as possible. See the [`README`](system-tests/README.md) for more information.
492
492
493
-
Please refer to each packages' `README.md` which documents how to run tests. It is not feasible to try to run all of the tests together. We run our entire test fleet across over a dozen containers in CI.
493
+
Additionally, we test the code by running it against various other example projects in CI. See CI badges and links at the top of this document.
494
494
495
495
If you're curious how we manage all of these tests in CI check out our [`circle.yml`](circle.yml) file found in the root `cypress` directory.
0 commit comments