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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -461,7 +461,7 @@ There are also a set of system tests in [`system-tests`](system-tests) which att
461
461
462
462
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.
463
463
464
-
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.
464
+
If you're curious how we manage all of these tests in CI check out our [CircleCI config](.circleci/config.yml).
465
465
466
466
#### Docker
467
467
@@ -474,7 +474,7 @@ Sometimes tests pass locally, but fail in CI. Our CI environment is dockerized.
474
474
$ yarn docker
475
475
```
476
476
477
-
There is a script [scripts/run-docker-local.sh](scripts/run-docker-local.sh) that runs the cypress image (see [circle.yml](circle.yml) for the current image name).
477
+
There is a script [scripts/run-docker-local.sh](scripts/run-docker-local.sh) that runs the cypress image (see [CircleCI config](.circleci/config.yml) for the current image name).
478
478
479
479
The image will start and will map the root of the repository to `/cypress` inside the image. Now you can modify the files using your favorite environment and rerun tests inside the docker environment.
In `develop`, `master`, and any other branch configured in [`circle.yml`](../circle.yml), the Cypress binary and npm package are built and uploaded to `cdn.cypress.io`. Then, tests are run, using a variety of real-world example repositories.
3
+
In `develop`, `master`, and any other branch configured in [the CircleCI config](../.circleci/config.yml), the Cypress binary and npm package are built and uploaded to `cdn.cypress.io`. Then, tests are run, using a variety of real-world example repositories.
4
4
5
5
Two main strategies are used to spawn these test projects:
6
6
@@ -9,7 +9,7 @@ Two main strategies are used to spawn these test projects:
9
9
10
10
## `test-binary-against-repo` jobs
11
11
12
-
A number of CI jobs in `circle.yml` clone test projects and run tests as part of `cypress-io/cypress`'s CI pipeline.
12
+
A number of CI jobs in `.circleci/config.yml` clone test projects and run tests as part of `cypress-io/cypress`'s CI pipeline.
13
13
14
14
You can find a list of test projects that do this by searching for usage of the `test-binary-against-repo` step.
15
15
@@ -19,4 +19,4 @@ One advantage to local CI is that it does not require creating commits to anothe
19
19
20
20
## `binary-system-tests`
21
21
22
-
System tests in `/system-tests/test-binary` are run against the built Cypress App in CI. For more details, see the [README](../system-tests/README.md).
22
+
System tests in `/system-tests/test-binary` are run against the built Cypress App in CI. For more details, see the [README](../system-tests/README.md).
- Update the Docker `image`s to the new matching `browsers` image.
48
48
- Update the `xcode` version to one with the same major Node.js version bundled. There is usually not an exact match, this is ok as long as the major version number as the same.
49
49
-[ ] Do a global search for the old Node.js version to identify any new areas that may need updating/unification, and update those locations (and this document!)
50
50
-[ ]**Manually smoke test `cypress open`.** Upgrading Electron can break the `desktop-gui` in unexpected ways. Since testing in this area is weak, double-check that things like launching `cypress open`, signing into the Dashboard, and launching Electron tests still work.
51
-
-[ ]**Fix failing tests.** Usually, these are due to breaking changes in either Node.js or Electron. Check the changelogs of both to find relevant changes.
51
+
-[ ]**Fix failing tests.** Usually, these are due to breaking changes in either Node.js or Electron. Check the changelogs of both to find relevant changes.
0 commit comments