Skip to content

Commit c9f6afa

Browse files
committed
Remove mentions of npx @replayio/cypress run
1 parent 6a9d3f4 commit c9f6afa

File tree

7 files changed

+17
-206
lines changed

7 files changed

+17
-206
lines changed

src/app/basics/test-suites/overview/page.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ At the first glance, that recording may look like a series of snapshots of your
149149

150150
{% accordion-item title="When do I use Replay with my tests?" %}
151151

152-
There are a [couple of strategies](/reference/ci-workflows/recording-strategies) you can adopt, but generally you can use Replay Browser with every test run on your CI, as there is both short-term and long-term value.
152+
There are a couple of strategies you can adopt, but generally you can use Replay Browser with every test run on your CI, as there is both short-term and long-term value.
153153

154154
When a test fails on CI, you don’t need to replicate it locally anymore. A replay captures your test run **exactly** as it happened and will provide you better insight than if you tried to locally reproduce an issue from CI.
155155

src/app/reference/ci-workflows/recording-strategies/page.md

+3-31
Original file line numberDiff line numberDiff line change
@@ -3,42 +3,14 @@ title: Recording strategies
33
description: Depending on what problem you’re trying to solve, there are two primary ways of using Replay.
44
---
55

6-
## Record failures on PRs
6+
## Record on PRs
77

8-
This is useful for debugging failing tests in pull requests. It only records failing tests so there’s minimal overhead, and those replays will be available for debugging immediately after tests finish.
9-
10-
Run your tests and pass the mode `record-on-retry` .
11-
12-
{% tabs labels=["npm", "yarn", "pnpm"] %}
13-
{% tab %}
14-
15-
```sh
16-
npx @replayio/cypress run --mode record-on-retry
17-
```
18-
19-
{% /tab %}
20-
{% tab %}
21-
22-
```sh
23-
yarn @replayio/cypress run --mode record-on-retry
24-
```
25-
26-
{% /tab %}
27-
{% tab %}
28-
29-
```sh
30-
pnpx @replayio/cypress run --mode record-on-retry
31-
```
32-
33-
{% /tab %}
34-
{% /tabs %}
8+
This is useful for debugging failing tests in pull requests. It records tests and those replays will be available for debugging immediately after tests finish.
359

3610
## Record all on merge to master
3711

38-
This is useful for busting flakes. It only records failing tests so there’s minimal overhead, and those replays will be available for debugging immediately after tests finish.
39-
4012
Run your tests as usual, but set the trigger to only run on merge to master.
4113

4214
{% callout type="link" title="Upload strategies" href="/reference/ci-workflows/upload-strategies" %}
43-
You have the flexibility to choose not only when to record but also when to upload your recordings. For details on various uploading strategies, [see the documentation](/reference/ci-workflows/upload-strategies).
15+
You have the flexibility to choose when to upload your recordings. For details on various uploading strategies, [see the documentation](/reference/ci-workflows/upload-strategies).
4416
{% /callout %}

src/app/reference/test-runners/cypress-io/github-actions/page.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,6 @@ Add a new step to run after your Cypress tests for uploading the replays:
7575
api-key: ${{ secrets.REPLAY_API_KEY }}
7676
```
7777

78-
{% callout title="Recording strategies" %}
79-
There are different strategies for creating your replays. For example you can use Replay only when retrying a failed test, or choose to upload recordings from failed tests only. See [docs on recording strategies](/reference/ci-workflows/recording-strategies) to learn more.
78+
{% callout title="Upload strategies" %}
79+
There are different strategies for uploading your replays. For example you can use Replay only when retrying a failed test, or choose to upload recordings from failed tests only. See [docs on upload strategies](/reference/ci-workflows/upload-strategies) to learn more.
8080
{% /callout %}

src/app/reference/test-runners/cypress-io/overview/page.md

-7
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,6 @@ npx cypress run --browser replay-chromium
1919
description="Learn how to get started with Cypress and Replay"
2020
/%}
2121

22-
{% quick-link
23-
title="Recording options"
24-
icon="record"
25-
href="/reference/test-runners/cypress-io/recording-options"
26-
description="See what recording options are available for Cypress.io and Replay"
27-
/%}
28-
2922
{% quick-link
3023
title="GitHub Actions"
3124
icon="github"

src/app/reference/test-runners/cypress-io/recording-options/page.md

-154
This file was deleted.

src/lib/navigation.ts

-8
Original file line numberDiff line numberDiff line change
@@ -229,10 +229,6 @@ export const navigation: Record<NavigationNames, NavigationItem[]> = {
229229
title: 'Debugging tests',
230230
href: '/reference/test-runners/cypress-io/debugging-tests',
231231
},
232-
{
233-
title: 'Recording options',
234-
href: '/reference/test-runners/cypress-io/recording-options',
235-
},
236232
{
237233
title: 'GitHub actions',
238234
href: '/reference/test-runners/cypress-io/github-actions',
@@ -309,10 +305,6 @@ export const navigation: Record<NavigationNames, NavigationItem[]> = {
309305
title: 'Generate API key',
310306
href: '/reference/ci-workflows/generate-api-key',
311307
},
312-
{
313-
title: 'Recording strategies',
314-
href: '/reference/ci-workflows/recording-strategies',
315-
},
316308
{
317309
title: 'Upload strategies',
318310
href: '/reference/ci-workflows/upload-strategies',

vercel.json

+11-3
Original file line numberDiff line numberDiff line change
@@ -570,7 +570,7 @@
570570
},
571571
{
572572
"source": "/test-suites/_archive/ci-integration/circle-ci",
573-
"destination": "/reference/ci-workflows/recording-strategies"
573+
"destination": "/reference/ci-workflows/upload-strategies"
574574
},
575575
{
576576
"source": "/test-suites/_archive/ci-integration/github-actions",
@@ -895,7 +895,11 @@
895895
},
896896
{
897897
"source": "/ci-workflows/recording-strategies",
898-
"destination": "/reference/ci-workflows/recording-strategies"
898+
"destination": "/reference/ci-workflows/upload-strategies"
899+
},
900+
{
901+
"source": "/reference/ci-workflows/recording-strategies",
902+
"destination": "/reference/ci-workflows/upload-strategies"
899903
},
900904
{
901905
"source": "/ci-workflows/upload-strategies",
@@ -991,7 +995,11 @@
991995
},
992996
{
993997
"source": "/test-runners/cypress-io/recording-options",
994-
"destination": "/reference/test-runners/cypress-io/recording-options"
998+
"destination": "/reference/test-runners/cypress-io"
999+
},
1000+
{
1001+
"source": "/reference/test-runners/cypress-io/recording-options",
1002+
"destination": "/reference/test-runners/cypress-io"
9951003
},
9961004
{
9971005
"source": "/test-runners/cypress-io/troubleshooting-guide",

0 commit comments

Comments
 (0)