Skip to content

Commit 1f0ece1

Browse files
Update CircleCI config link in Development.md (#831)
Co-authored-by: Jennifer Shehane <[email protected]>
1 parent 22bd5e9 commit 1f0ece1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Development.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Development
22

3-
- when adding a new example, add a matching test job to [circle.yml](circle.yml)
3+
- when adding a new example, add a matching test job to [.circleci/config.yml](.circleci/config.yml)
44
- there is a script [test-examples.js](test-examples.js) useful to run all examples one by one
55
* note that the script only runs an example if it has `npm run test:ci` script command.
66

@@ -78,7 +78,7 @@ npm run test:ci:firefox
7878

7979
### Recipes for upcoming Test Runner versions
8080

81-
When a new version of Test Runner is about to be released, but is not yet available, you can still write recipes. Just place the new recipes into a branch with the name matching the upcoming version, like [3.7.0](https://github.com/cypress-io/cypress-example-recipes/tree/3.7.0) that will be merged once the version v3.7.0 is officially released and we can upgrade. To run the branch _before_ the official NPM release, you can use [commit-message-install](http://github.com/bahmutov/commit-message-install) utility, that is already set up in [circle.yml](circle.yml) `build` job. It runs after "normal" `npm ci` installation and can install new pre-release version of Cypress based on the commit message. The installation uses a special `json` block object if found inside the commit's message body. A typical commit can be found [here](https://github.com/cypress-io/cypress/commit/b03b25c258990966cbc99e50796c039abbf2f893#commitcomment-36028805) - these comments are posted by CI automatically when each Test Runner `develop` commit is built.
81+
When a new version of Test Runner is about to be released, but is not yet available, you can still write recipes. Just place the new recipes into a branch with the name matching the upcoming version, like [3.7.0](https://github.com/cypress-io/cypress-example-recipes/tree/3.7.0) that will be merged once the version v3.7.0 is officially released and we can upgrade. To run the branch _before_ the official NPM release, you can use [commit-message-install](http://github.com/bahmutov/commit-message-install) utility, that is already set up in [.circleci/config.yml](.circleci/config.yml) `build` job. It runs after "normal" `npm ci` installation and can install new pre-release version of Cypress based on the commit message. The installation uses a special `json` block object if found inside the commit's message body. A typical commit can be found [here](https://github.com/cypress-io/cypress/commit/b03b25c258990966cbc99e50796c039abbf2f893#commitcomment-36028805) - these comments are posted by CI automatically when each Test Runner `develop` commit is built.
8282

8383
Simply commit an empty set of changes with `git commit --allow-empty` and set the message body like this one
8484

@@ -110,7 +110,7 @@ Once the new Cypress version is published, merge the branch.
110110

111111
## Fighting flake
112112

113-
If you notice a recipe test failing sometimes, run more of it! In [circle.yml](circle.yml) a job can take `repeat: N` parameter to run the recipe N times. Increase the number of times to run the recipe to flush out flaky tests and fix them.
113+
If you notice a recipe test failing sometimes, run more of it! In [.circleci/config.yml](.circleci/config.yml) a job can take `repeat: N` parameter to run the recipe N times. Increase the number of times to run the recipe to flush out flaky tests and fix them.
114114

115115
Example recipe to run 5 times
116116

0 commit comments

Comments
 (0)