-
Notifications
You must be signed in to change notification settings - Fork 1.1k
docs: adds --posix-exit-codes cli flag for run mode #6284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release/15.4.0
Are you sure you want to change the base?
Conversation
cypress-documentation
|
Project |
cypress-documentation
|
Branch Review |
feat/posix-exit-codes
|
Run status |
|
Run duration | 04m 24s |
Commit |
|
Committer | Cacie Prins |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
0
|
|
0
|
|
309
|
View all changes introduced in this branch ↗︎ |
UI Coverage
10.86%
|
|
---|---|
|
2482
|
|
3
|
Accessibility
97.21%
|
|
---|---|
|
1 critical
3 serious
4 moderate
0 minor
|
|
28
|
This comment was marked as resolved.
This comment was marked as resolved.
This is the default behavior as described in the previous two paragraphs. We are considering whether or not to modify the default behavior to align to posix standards as a breaking change in a later release. |
#### `cypress run --posix-exit-codes` {#cypress-run-posix-exit-codes} | ||
Exit with POSIX exit code of 1 when there are test failures or if Cypress could not run. | ||
```shell | ||
cypress run --posix-exit-codes | ||
``` | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe cross-link here to the section #Exit-code
?
I completely missed this section when I glanced at the change 🤭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea! Updated here 524b211
... | ||
``` | ||
```text | ||
## print exit code on Mac or Linux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... | |
``` | |
```text | |
## print exit code on Mac or Linux | |
... | |
## print exit code on Mac or Linux |
Merge into one code block like the other examples above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
||
## 15.4.0 | ||
|
||
_Released 9/30/2025_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_Released 9/30/2025_ | |
_Released 10/7/2025_ |
| `--no-runner-ui` | [Hides the Cypress Runner UI](#cypress-run-no-runner-ui) | | ||
| `--parallel` | [Run recorded specs in parallel across multiple machines](#cypress-run-parallel) | | ||
| `--port`,`-p` | [Override default port](#cypress-run-port-lt-port-gt) | | ||
| `--posix-exit-codes` | [Exit with a POSIX-compliant exit code](#cypress-run-posix-exit-codes) rather than the number of failed tests. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This option needs to be added to the Module API doc: https://deploy-preview-6284--cypress-docs.netlify.app/app/references/module-api
Adds
--posix-exit-codes
flag, which disables exiting with the number of tests fail. This is preliminary to adding a custom (but compliant) exit code for terminal cloud API failures during recording or parallel runs.See: cypress-io/cypress#32485