Skip to content

Commit 6af2913

Browse files
AtofStrykerMikeMcC399danjohansenconsultingcacieprinsjennifer-shehane
authored
chore: merge dev into 15 (#6172)
* Add Windows 2025 to supported OS list (#6142) * New user roles and permissions defined (#6143) * chore: release 14.3.0 documentation (#6144) * feat: documentation for the press() command (#6135) * docs for the press() command, including a callout in the accessibility guide * add press to TOC * Move some content around, mention accesiibility * remove 'focus' note * Document Keyboard.Keys * update reference to command * Update example to be a little more real case * Add another example of autocomplete with tab * Add link to keyboard api page * Fix version number for introduction * Fix broken link * alphabetize see also * Update package.json Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * Fix broken link * lint --------- Co-authored-by: Jennifer Shehane <jennifer@cypress.io> Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * chore: add 14.3.0 changelog to documentation * Update docs/app/guides/accessibility-testing.mdx * Update docs/app/references/changelog.mdx Co-authored-by: Bill Glesias <bglesias@gmail.com> --------- Co-authored-by: Cacie Prins <cacieprins@users.noreply.github.com> Co-authored-by: Jennifer Shehane <jennifer@cypress.io> Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * Correct parameter usage for click() in shadow.mdx (#6145) * Update shadow.mdx - Update the suggestion to pass 'top' to cy.click() using the options defined in cy.click()'s documentation * Update shadow.mdx Add missing quote * Update shadow.mdx One-line for prettier reasons * Correct command syntax (#6148) Adds the missing `s` to `Cypress.Command.overwrite()` * extend pnpm config instructions (#6149) * fix cy.origin() "yielding a value" example (#6152) * Update results-api.mdx (#6150) * chore: add 14.3.1 changelog (#6153) * chore: add 14.3.1 changelog * Update docs/app/references/changelog.mdx Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * empty commit to rekick build --------- Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * docs: harmonize on injectDocumentDomain removal in future version (#6154) * Add experimentalSessionAndOrigin removed comment to origin video (#6158) * Fix "cy.visit() succeeded, but commands are timing out" error example (#6157) * Cross-link cy.origin and injectDocumentDomain (#6156) * chore: add cypress 14.3.2 changelog (#6160) * Change 'add on' to 'premium solution' for UI Cov & a11y products (#6162) * UI Coverage and Branch Review updates (#6167) * add AQ links and button space * use onlinks for demo vids * update Cypress * content updates * content tweaks * add last images * lint-fix * simplify * add detail view docs and clean up * lint fix * Update docs/cloud/get-started/introduction.mdx Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * Update docs/ui-coverage/core-concepts/compare-reports.mdx Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * Update docs/ui-coverage/core-concepts/compare-reports.mdx Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> * revert cypress version bump * restore package-lock * remove yarn lockfile * Update docs/app/get-started/why-cypress.mdx Co-authored-by: Tyler Biethman <tbiethman@gmail.com> * Update docs/cloud/features/branch-review.mdx Co-authored-by: Tyler Biethman <tbiethman@gmail.com> * Update docs/cloud/features/branch-review.mdx Co-authored-by: Tyler Biethman <tbiethman@gmail.com> --------- Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Co-authored-by: Tyler Biethman <tbiethman@gmail.com> * chore: add 14.3.3 changelog (#6171) * chore: add 14.3.3 changelog * Update docs/app/references/changelog.mdx Co-authored-by: Matt Schile <mschile@cypress.io> --------- Co-authored-by: Matt Schile <mschile@cypress.io> * Rework instructions for missing Cypress binary in CI (#6170) * Node.js 18 EOL (#6165) * Add quoting advice for PowerShell CLI options (#6169) * Add quoting advice for PowerShell CLI options * Fix --config typo Co-authored-by: Jennifer Shehane <shehane.jennifer@gmail.com> --------- Co-authored-by: Jennifer Shehane <shehane.jennifer@gmail.com> * Bump Cypress Docker versions in examples to Node.js 22.15.0 LTS (#6161) --------- Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Co-authored-by: danjohansenconsulting <133032924+danjohansenconsulting@users.noreply.github.com> Co-authored-by: Cacie Prins <cacieprins@users.noreply.github.com> Co-authored-by: Jennifer Shehane <jennifer@cypress.io> Co-authored-by: Matthew Sbar <sbarmatthew@gmail.com> Co-authored-by: Tim Rayers <tprayers@gmail.com> Co-authored-by: Emily Wisniewski (Rohrbough) <emilyrohrbough@users.noreply.github.com> Co-authored-by: Mark Noonan <mark@cypress.io> Co-authored-by: Tyler Biethman <tbiethman@gmail.com> Co-authored-by: Matt Schile <mschile@cypress.io> Co-authored-by: Jennifer Shehane <shehane.jennifer@gmail.com>
1 parent 7ecc261 commit 6af2913

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+722
-332
lines changed

docs/accessibility/changelog.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ sidebar_position: 200
2424

2525
## Week of 2/24/2025
2626

27-
- [Cypress Accessibility Branch Review](/accessibility/core-concepts/comparing-reports) has entered beta. Read the docs to learn how to compare runs and automatically spot newly introduced issues.
27+
- [Cypress Accessibility Branch Review](/accessibility/core-concepts/compare-reports) has entered beta. Read the docs to learn how to compare runs and automatically spot newly introduced issues.
2828

2929
## Week of 1/13/2025
3030

docs/accessibility/core-concepts/comparing-reports.mdx renamed to docs/accessibility/core-concepts/compare-reports.mdx

+6-43
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Comparing the results from different runs is useful in multiple scenarios.
2929
- **Detecting content issues**: Sometimes content editors can introduce accessibility issues unrelated to code changes. Seeing the example issues presented visually, in context, helps you quickly triage whether you are dealing with a recent code change issue, or a content authorship problem.
3030
- **Reviewing AI-generated code changes**: The increased use of AI to generate and/or review front-end code creates some increased risks of accessibility regressions making it to production. The increase or decrease of accessibility issues when reviewing a pull request helps you understand the impact of the change.
3131
- **Tracing the introduction of issues**: With dropdowns for each run, it's easy to rapidly compare different A and B runs to find the exact commit that introduced a problem.
32-
- **Demonstrating the resolution of issues**: Confirm the effect of your improvements, and share overview with your team to more quickly review code changes.
32+
- **Demonstrating the resolution of issues**: Confirm the effect of your improvements, and share the overview with your team to more quickly review code changes.
3333

3434
## Content of the report
3535

@@ -49,47 +49,8 @@ This organization of the report brings the most significant results to the top -
4949

5050
## How to compare runs
5151

52-
The first step is to get to the Branch Review area of Cypress Cloud, which will let you compare one branch against another - or different runs on the same branch, if needed. We refer to be baseline fun for comparison as the `base` run, and the changes we are comparing with as the `changed` run.
53-
54-
There are a number of ways to get to Branch Review depending on where you are looking at your Cypress results. In all cases, once you've picked a `changed` run, you can adjust the automatically-selected `base` run to any branch or run in the project.
55-
56-
### From a Pull Request
57-
58-
<DocsImage
59-
src="/img/accessibility/core-concepts/branch-review-pull-request.png"
60-
alt="A pull request comment from Cypress with an arrow pointing to the 'View all changes introduced in this branch' link. Test results and some accessibility score and violation information is also visible in the comment. The project has an 86.86% accessibility score, with 9 failed elements. Failed rule counts are 1 critical, 1 serious, 3 moderate, and 0 minor."
61-
/>
62-
63-
Click the "View all changes introduced in this branch" link at the bottom of the Test Results table. You will enter branch review with the current PR's branch and latest run pre-selected as the "changed" run.
64-
65-
### From the run list
66-
67-
Click the branch name associated with the run. This will take you to Branch Review with that branch's newest run pre-selected as the `changed` run.
68-
69-
<DocsImage
70-
src="/img/accessibility/core-concepts/branch-review-run-card.png"
71-
alt="A couple of cards showing various details about Cypress test runs, including pass/fail counts and metadata. An arrow points to the branch name."
72-
/>
73-
74-
### From the project list
75-
76-
<DocsImage
77-
src="/img/accessibility/core-concepts/branch-review-project-card.png"
78-
width="40%"
79-
alt="A card showing the name of an example project and related branches to choose."
80-
/>
81-
82-
The project card shows three active branches for the project. You can click through to any of these to enter Branch Review with the newest run on that branch pre-selected as the `changed` run.
83-
84-
### From the main navigation
85-
86-
<DocsImage
87-
src="/img/accessibility/core-concepts/branch-review-side-nav.png"
88-
width="40%"
89-
alt="The main Cypress Cloud navigation showing Latest Runs, Branches, and Analytics menu items. An arrow points to Branches."
90-
/>
91-
92-
When inside of a project, you can select "Branches" in the main navigation to see a full, filterable list of available branches and choose one to set as the `changed` run.
52+
The first step is to get to the [Branch Review](/cloud/features/branch-review.mdx) area of Cypress Cloud, which will let you compare one branch against another - or different runs on the same branch, if needed.
53+
You can access this area by clicking the branch name associated with a run, or in several other ways. [Learn more about how to compare runs](/cloud/features/branch-review.mdx).
9354

9455
## FAQ
9556

@@ -99,9 +60,11 @@ The best subjects to compare are passing runs that ran similar tests on the same
9960

10061
That said, it still possible and valid to compare runs from different points in time with different sets of test results, as long as you bear in mind all the potential sources of difference between the two runs, which you can evaluate for yourself as you explore the results.
10162

63+
In order to see unified changes for your entire test suite, you need to group all the tests together under a single Cypress run, for each report. Learn more about this in the [Branch Review Best Practices documentation](/cloud/features/branch-review#Best-Practices).
64+
10265
### What is the purpose of the Beta label?
10366

104-
This indicates the feature is ready for use and actively seeking feedback based on real usage of the current implementation. We have a few known issues to work through on our side before we consider this fully production-ready and remove the beta label. These issues only affect a subset of projects -- in most cases everything is working as intended. If you see anything unexpected, please hit the feedback button and let us know.
67+
This indicates the feature is ready for use and actively seeking feedback based on real usage of the current implementation. We have a few known issues to work through on our side before we consider this fully production-ready and remove the beta label. These issues only affect a subset of projects -- in most cases everything is working as intended. If you see anything unexpected, please use the feedback button and let us know.
10568

10669
### Why do I see some views (pages or components) changing from run-to-run?
10770

docs/accessibility/core-concepts/how-it-works.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Cypress Accessibility seamlessly integrates accessibility testing into your deve
1515
1. **Processing**: When your run completes, the final specs are processed for accessibility checks. Earlier specs have already entered processing and are likely completed by the end of the run.
1616
1. **Organizing Views**: Cypress Cloud groups Views (pages and components) rendered during the run, merging and deduplicating across tests. This ensures page-level results and live DOM snapshots are organized effectively.
1717
1. **Generating reports**: A combined "rule-level" report is created, summarizing all detected accessibility violations.
18-
1. **Displaying results**: Results are displayed in Cypress Cloud in the run details area as well as in [Branch Review](/accessibility/core-concepts/comparing-reports) for comparing runs. Accessibility is also flagged in integrations (e.g., Slack, GitHub/GitLab comments), and accessible via the [Results API](/accessibility/results-api) for optional CI pipeline actions (e.g., failing builds based on unmet standards).
18+
1. **Displaying results**: Results are displayed in Cypress Cloud in the run details area as well as in [Branch Review](/accessibility/core-concepts/compare-reports) for comparing runs. Accessibility is also flagged in integrations (e.g., Slack, GitHub/GitLab comments), and accessible via the [Results API](/accessibility/results-api) for optional CI pipeline actions (e.g., failing builds based on unmet standards).
1919

2020
## About Axe Core®
2121

docs/accessibility/get-started/introduction.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Cypress Accessibility adds detailed accessibility checks and workflows in Cypres
2727
label="See a demo"
2828
icon="action-play-small"
2929
className="!mb-2 mr-1"
30-
href="https://www.loom.com/share/eedb1d18c22942d39a5ed2471ae72788?sid=e39f791e-c0b3-4efc-9770-cbfac403c3b9"
30+
href="https://on.cypress.io/accessibility-demo-video"
3131
/>
3232
<Btn
3333
label=" Explore an example project"
@@ -75,7 +75,7 @@ From there, you can integrate with CI to set your own standards for handling the
7575
href="/accessibility/guides/detect-changes"
7676
aria-labelledby="card-title-8"
7777
>
78-
<Icon name="chart-line" />
78+
<Icon name="shield-halved" />
7979
<h3 id="card-title-8">Detect and manage changes</h3>
8080
<p>
8181
Compare reports in detail to review only _new_ accessibility issues, use

docs/accessibility/guides/detect-changes.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ sidebar_position: 70
1111

1212
Cypress Accessibility supports three main paths to observing and acting on changes in the accessibility report for your projects:
1313

14-
- Run comparisons with [Branch Review](/accessibility/core-concepts/comparing-reports)
14+
- Run comparisons with [Branch Review](/accessibility/core-concepts/compare-reports)
1515
- The [Results API](/accessibility/results-api) to fail builds or trigger alerts when results don't meet your standards
1616
- [Analytics](/cloud/features/analytics/enterprise-reporting#Cypress-Accessibility) for high-level trend-spotting and analysis
1717

@@ -33,7 +33,7 @@ Use Branch review when reviewing a pull request made by another developer or bef
3333

3434
Since this reduces the amount of violations to review to just what was affected by the PR code changes, you won't spend any time looking for what's relevant -- and if there is no difference, you'll know your PR does not affect the accessibility score and is safe to merge.
3535

36-
See the main [Accessibility Branch Review docs](/accessibility/core-concepts/comparing-reports) for a video demo of this workflow.
36+
See the main [Accessibility Branch Review docs](/accessibility/core-concepts/compare-reports) for a video demo of this workflow.
3737

3838
#### Compare reports during local development (without waiting for CI)
3939

docs/accessibility/results-api.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -322,7 +322,7 @@ run-cypress:
322322
pipeline {
323323
agent {
324324
docker {
325-
image 'cypress/base:22.12.0'
325+
image 'cypress/base:22.15.0'
326326
}
327327
}
328328

@@ -393,7 +393,7 @@ version: 2.1
393393
jobs:
394394
linux-test:
395395
docker:
396-
- image: cypress/base:22.12.0
396+
- image: cypress/base:22.15.0
397397

398398
working_directory: ~/repo
399399
steps:

docs/api/commands/focus.mdx

+1
Original file line numberDiff line numberDiff line change
@@ -159,4 +159,5 @@ the following:
159159
- [`.blur()`](/api/commands/blur)
160160
- [`.click()`](/api/commands/click)
161161
- [`cy.focused()`](/api/commands/focused)
162+
- [`cy.press()`](/api/commands/press)
162163
- [`.type()`](/api/commands/type)

docs/api/commands/origin.mdx

+11-6
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,11 @@ doc.
4040

4141
Cypress no longer injects `document.domain` by default, which means `cy.origin()`
4242
must now be used to navigate between any two origins in the same test, even if
43-
the two origins are in the same superdomain. This behavior can be disabled by setting
44-
the `injectDocumentDomain` configuration option to `true`, to allow a smooth transition
45-
of tests to the new behavior. This configuration option will be removed in a future version of Cypress.
43+
the two origins are in the same superdomain.
44+
This behavior can be disabled by setting the
45+
[injectDocumentDomain](/app/references/configuration#injectDocumentDomain) configuration option to `true`,
46+
to allow a smooth transition of tests to the new behavior.
47+
This configuration option will be removed in a future version of Cypress.
4648

4749
:::
4850

@@ -191,7 +193,7 @@ will not work:
191193
cy.origin('https://example.cypress.io', () => {
192194
cy.visit('/')
193195
cy.get('h1') // Yields an element, which can't be serialized...
194-
}).contains('CYPRESS') // ...so this will fail
196+
}).contains('Kitchen Sink') // ...so this will fail
195197
```
196198

197199
Instead, you must explicitly yield a serializable value:
@@ -201,8 +203,8 @@ Instead, you must explicitly yield a serializable value:
201203
```js
202204
cy.origin('https://example.cypress.io', () => {
203205
cy.visit('/')
204-
cy.get('h1').invoke('textContent') // Yields a string...
205-
}).should('equal', 'CYPRESS') // 👍
206+
cy.get('h1').invoke('text') // Yields a string...
207+
}).should('equal', 'Kitchen Sink') // 👍
206208
```
207209

208210
### Navigating to secondary origin with cy.visit
@@ -367,6 +369,9 @@ Cypress.Commands.add('login', (username, password) => {
367369
In this video we walk through how to test multiple origins in a single test. We
368370
also look at how to use the `cy.session()` command to cache session information
369371
and reuse it across tests.
372+
The configuration option `experimentalSessionAndOrigin`, mentioned in the video, is not used
373+
since [Cypress 12.0.0](https://docs.cypress.io/app/references/changelog#12-0-0)
374+
and the associated functionality is enabled by default.
370375

371376
## Notes
372377

docs/api/commands/press.mdx

+134
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
---
2+
title: 'cy.press() | Cypress Documentation'
3+
description: Trigger native key events in your application to simulate keyboard interactions.
4+
sidebar_label: press
5+
slug: /api/commands/press
6+
componentSpecific: false
7+
---
8+
9+
<ProductHeading product="app" />
10+
11+
# press
12+
13+
Trigger native key events in your application to simulate keyboard interactions.
14+
15+
A `keydown`, `press`, and `keyup` event will be dispatched directly to the browser window.
16+
17+
Unlike `cy.type()`, which is best for typing character keys, `cy.press()` will dispatch real keyboard events rather than simulated ones. This command is especially useful when testing focus management and keyboard navigation patterns which are critical for [accessibility testing](/app/guides/accessibility-testing) and great keyboard UX.
18+
19+
Currently, the only key supported is `Tab`.
20+
21+
:::caution
22+
23+
<strong>Supported Browsers:</strong>
24+
This command is supported in chromium browsers and Firefox versions >= v135. WebKit
25+
is not supported. This command will fail if executed in a browser that does not support
26+
it.
27+
28+
:::
29+
30+
## Syntax
31+
32+
```javascript
33+
cy.press(key)
34+
cy.press(key, options)
35+
```
36+
37+
## Signature
38+
39+
```typescript
40+
interface PressCommand {
41+
(
42+
key: KeyPressSupportedKeys,
43+
options?: Partial<Cypress.Loggable> & Partial<Cypress.Timeoutable>
44+
): void
45+
}
46+
```
47+
48+
## Usage
49+
50+
<Icon name="check-circle" color="green" /> **Correct Usage**
51+
52+
```javascript
53+
cy.get('input.first').focus()
54+
cy.press(Cypress.Keyboard.Keys.TAB)
55+
cy.get('input.second').should('have.focus')
56+
```
57+
58+
<Icon name="exclamation-triangle" color="red" /> **Incorrect Usage**
59+
60+
```javascript
61+
cy.get('input.first').focus()
62+
cy.press(Cypress.Keyboard.Keys.TAB)
63+
// Errors because press yields null
64+
.should('have.focus')
65+
```
66+
67+
### Arguments
68+
69+
<Icon name="angle-right" /> **key _(String)_**
70+
71+
The key to press. The supported values are available on [`Cypress.Keyboard.Keys`](/api/cypress-api/keyboard-api), and may change from time to time. It's recomended that you reference these values from `Cypress.Keyboard.Keys` rather than passing in a string.
72+
73+
### Supported Keys
74+
75+
| Reference | Value |
76+
| --------------------------- | ------- |
77+
| `Cypress.Keyboard.Keys.TAB` | `"Tab"` |
78+
79+
<Icon name="angle-right" /> **options _(Object)_**
80+
81+
Pass in an options object to change the default behavior of `.press()`.
82+
83+
| Option | Default | Description |
84+
| --------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
85+
| `log` | `true` | Displays the command in the [Command log](/app/core-concepts/open-mode#Command-Log) |
86+
| `timeout` | [`defaultCommandTimeout`](/app/references/configuration#Timeouts) | Time to wait for `cy.press()` to resolve before timing out |
87+
88+
<HeaderYields />
89+
90+
- `cy.press()` yields `null`.
91+
92+
## Examples
93+
94+
### Test focus order of tab
95+
96+
```js
97+
it('moves focus to the next form element when pressing Tab', () => {
98+
cy.visit('/my-login')
99+
cy.get('input.email').type('username')
100+
cy.press(Cypress.Keyboard.Keys.TAB)
101+
cy.get('input.password').should('have.focus')
102+
})
103+
```
104+
105+
### Test autocomplete of search input with tab
106+
107+
```js
108+
it('autocompletes search input when pressing Tab', () => {
109+
cy.get('[data-cy="search"]').type('cy')
110+
cy.press(Cypress.Keyboard.Keys.TAB)
111+
cy.get('[data-cy="search"]').should('have.value', 'cypress')
112+
})
113+
```
114+
115+
## Notes
116+
117+
### Transient activation
118+
119+
By dispatching native keyboard events to the browser, this command will cause the browser to enter [Transient activation](https://developer.mozilla.org/en-US/docs/Glossary/Transient_activation) state.
120+
121+
If your application prevents the default behavior of the `beforeunload` event, this may cause issues when navigating away from the current page.
122+
123+
## History
124+
125+
| Version | Changes |
126+
| ----------------------------------- | ---------------------------- |
127+
| [14.3.0](/app/references/changelog) | Added the `.press()` command |
128+
129+
## See also
130+
131+
- [`Cypress.Keyboard`](/api/cypress-api/keyboard-api)
132+
- [`.focus()`](/api/commands/focus)
133+
- [`.focused()`](/api/commands/focused)
134+
- [`.type()`](/api/commands/type)

docs/api/commands/shadow.mdx

+2-5
Original file line numberDiff line numberDiff line change
@@ -96,13 +96,10 @@ When working with `cy.click()`, it sometimes won't click the right element in
9696
Chrome. It's happening because of
9797
[the ambiguity in spec](https://bugs.chromium.org/p/chromium/issues/detail?id=1188919&q=shadowRoot%20elementFromPoint&can=2).
9898

99-
In this case, pass `{ position: 'top' }` to `cy.click()` like below:
99+
In this case, pass `'top'` to `cy.click()` like below:
100100

101101
```js
102-
cy.get('#element')
103-
.shadow()
104-
.find('[data-test-id="my-button"]')
105-
.click({ position: 'top' })
102+
cy.get('#element').shadow().find('[data-test-id="my-button"]').click('top')
106103
```
107104

108105
## Command Log

docs/api/commands/type.mdx

+1
Original file line numberDiff line numberDiff line change
@@ -664,5 +664,6 @@ following:
664664
- [`.clear()`](/api/commands/clear)
665665
- [`.click()`](/api/commands/click)
666666
- [`.focus()`](/api/commands/focus)
667+
- [`cy.press()`](/api/commands/press)
667668
- [`.submit()`](/api/commands/submit)
668669
- [`Cypress.Keyboard`](/api/cypress-api/keyboard-api)

docs/api/cypress-api/custom-commands.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ There are two API available for adding custom commands:
1717

1818
- [`Cypress.Commands.add()`](#Syntax) - use to add a custom command to use when
1919
writing tests
20-
- [`Cypress.Command.overwrite()`](#Overwrite-Existing-Commands) - use to
20+
- [`Cypress.Commands.overwrite()`](#Overwrite-Existing-Commands) - use to
2121
override an existing built-in Cypress command or reserved internal function.
2222
**Caution:** this overrides it for Cypress as well and could impact how
2323
Cypress behaves.

0 commit comments

Comments
 (0)