Remove mentions of npx @replayio/cypress run (#202)

* Remove mentions of `npx @replayio/cypress run`

* remove recording strategies

* extend failed links summary with source

* update `vercel.json`

Author: Andarist

scripts/checkLinks.ts

@@ -118,23 +118,27 @@ async function main(): Promise<void> {
   for (const [index, file] of files.entries()) {
     const { file: filePath, links } = file
     process.stdout.write(`${index + 1} ${filePath} `)
-    failedLinks.push(...(await checkLinksInFile(filePath, links)))
+    failedLinks.push(
+      ...(await checkLinksInFile(filePath, links)).map(
+        (l) => `${filePath}: ${l}`,
+      ),
+    )
     process.stdout.write('\n')
   }
 
   console.log('Checking links in Vercel.json')
   failedLinks.push(
-    ...(await checkLinksInFile(
-      'vercel.json',
-      vercelConfig.redirects.map((l) => l.destination),
-    )),
+    ...(
+      await checkLinksInFile(
+        'vercel.json',
+        vercelConfig.redirects.map((l) => l.destination),
+      )
+    ).map((l) => `vercel.json: ${l}`),
   )
 
-  const dedupedFailedLinks = [...new Set(failedLinks)]
-
   if (failedLinks.length > 0) {
     console.error('\nThe following links are broken:')
-    for (const link of dedupedFailedLinks) {
+    for (const link of failedLinks) {
       console.error(link)
     }
     process.exit(1)

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

@@ -149,7 +149,7 @@ At the first glance, that recording may look like a series of snapshots of your
 
 {% accordion-item title="When do I use Replay with my tests?" %}
 
-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.
+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.
 
 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.
 

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

@@ -75,6 +75,6 @@ Add a new step to run after your Cypress tests for uploading the replays:
     api-key: ${{ secrets.REPLAY_API_KEY }}
 ```
 
-{% callout title="Recording strategies" %}
-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.
+{% callout title="Upload strategies" %}
+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.
 {% /callout %}

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

@@ -19,13 +19,6 @@ npx cypress run --browser replay-chromium
   description="Learn how to get started with Cypress and Replay"
 /%}
 
-{% quick-link
-  title="Recording options"
-  icon="record"
-  href="/reference/test-runners/cypress-io/recording-options"
-  description="See what recording options are available for Cypress.io and Replay"
-/%}
-
 {% quick-link
   title="GitHub Actions"
   icon="github"

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

@@ -229,10 +229,6 @@ export const navigation: Record<NavigationNames, NavigationItem[]> = {
               title: 'Debugging tests',
               href: '/reference/test-runners/cypress-io/debugging-tests',
             },
-            {
-              title: 'Recording options',
-              href: '/reference/test-runners/cypress-io/recording-options',
-            },
             {
               title: 'GitHub actions',
               href: '/reference/test-runners/cypress-io/github-actions',
@@ -309,10 +305,6 @@ export const navigation: Record<NavigationNames, NavigationItem[]> = {
           title: 'Generate API key',
           href: '/reference/ci-workflows/generate-api-key',
         },
-        {
-          title: 'Recording strategies',
-          href: '/reference/ci-workflows/recording-strategies',
-        },
         {
           title: 'Upload strategies',
           href: '/reference/ci-workflows/upload-strategies',

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

@@ -570,7 +570,7 @@
     },
     {
       "source": "/test-suites/_archive/ci-integration/circle-ci",
-      "destination": "/reference/ci-workflows/recording-strategies"
+      "destination": "/reference/ci-workflows/upload-strategies"
     },
     {
       "source": "/test-suites/_archive/ci-integration/github-actions",
@@ -895,7 +895,11 @@
     },
     {
       "source": "/ci-workflows/recording-strategies",
-      "destination": "/reference/ci-workflows/recording-strategies"
+      "destination": "/reference/ci-workflows/upload-strategies"
+    },
+    {
+      "source": "/reference/ci-workflows/recording-strategies",
+      "destination": "/reference/ci-workflows/upload-strategies"
     },
     {
       "source": "/ci-workflows/upload-strategies",
@@ -991,7 +995,11 @@
     },
     {
       "source": "/test-runners/cypress-io/recording-options",
-      "destination": "/reference/test-runners/cypress-io/recording-options"
+      "destination": "/reference/test-runners/cypress-io/overview"
+    },
+    {
+      "source": "/reference/test-runners/cypress-io/recording-options",
+      "destination": "/reference/test-runners/cypress-io/overview"
     },
     {
       "source": "/test-runners/cypress-io/troubleshooting-guide",