You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub upload action takes care of uploading your recordings during your CI test runs on GitHub. It enables you to filter the recordings you upload to Replay App.
Cypress team has created its [official GitHub Action](https://github.com/cypress-io/github-action). The action provides dependency installation, built-in caching, and multiple options for advanced workflow configuration.
6
-
7
-
Using this GitHub Action is optional and some teams prefer their own custom setup. Replay integrates well with both workflows, as shown in examples below
8
-
9
5
{% callout %}
10
-
These instructions assume that you have already installed [`@replayio/cypress`](https://www.npmjs.com/package/@replayio/cypress) plugin into your project. [Follow the instructions on this page](/basics/getting-started/record-your-cypress-tests) to learn how to install the plugin.
6
+
These instructions assume that you have already [set up your Cypress project](/basics/getting-started/record-your-cypress-tests).
11
7
{% /callout %}
12
8
13
-
## Using GitHub Actions with `cypress-io/github-action`
14
-
15
-
When using the Cypress [GitHub Action](https://github.com/cypress-io/github-action), the CI setup requires just a couple of lines of code. For the Cypress run itself, the `replay-chromium` browser needs to be passed in to create recordings.
16
-
17
-
After test run finishes, an additional step needs to be added to upload all the recordings using `@replayio/action-upload` action.
9
+
This example uses [Cypress GitHub Action](https://github.com/cypress-io/github-action) that provides dependency installation, built-in caching, and multiple options for advanced workflow configuration. For recording your test, the `replay-chromium` browser needs to be passed as a browser.
## Using GitHub Actions without `cypress-io/github-action`
44
-
45
-
Without using GitHub Actions and running your Cypress tests by calling a script, the main principles stay the same:
30
+
Running with Replay browser will create your replays. These are stored locally on your CI and need to be uploaded to Replay app once the test run is finished.
46
31
47
-
- you need to make sure to pass `REPLAY_API_KEY` to your test run
48
-
- add step to your pipeline to upload your replays
32
+
{% quick-links title="Learn more" %}
49
33
50
-
There are a couple of different ways to achieve this. For example, you can update your `package.json` file with a custom script that runs your Cypress tests with Replay Browser
"cy:run:replay": "cypress run --browser=replay-chromium" // new test script
56
-
}
57
-
```
34
+
{% quick-link
35
+
title="Upload strategies"
36
+
icon="uploadicon"
37
+
description="There are different strategies for uploading your replays such as uploading only on test flakes or failures."
38
+
href="/reference/ci-workflows/upload-strategies"
39
+
/%}
40
+
{% quick-link
41
+
title="GitHub upload action"
42
+
icon="github"
43
+
description="GitHub upload action takes care of uploading your recordings during your CI test runs on GitHub. It enables you to filter the recordings you upload to Replay App."
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.
0 commit comments