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
Checkly sets the following built-in environment variables on every Playwright Check Suite run. They provide information about the check execution environment, and allow you to distinguish between Checkly executions and local runs.
9
+
10
+
-**CHECKLY**: Set to `1` for all check runs executed by Checkly.
11
+
-**CHECKLY_RUN_SOURCE**: Indicates the manual or scheduled check run trigger. Use this variable to skip parts of your test suite in certain scenarios or adjust the check run configuration. Possible values include:
12
+
-`CLI_DEPLOY`: Checks deployed using `npx checkly deploy` get their first run scheduled with this type.
13
+
-`DEPLOYMENT`: The check was triggered as part of a [CI/CD deployment](/integrations/ci-cd/github/deployments).
14
+
-`EDITOR`: The check was triggered from the editor page of a browser, multi step or API check.
15
+
-`GROUP_RUN_ALL`: The check was triggered as part of a group edit by a user clicking the "Run all checks" button.
16
+
-`SCHEDULE_NOW`: The check was triggered manually by a user clicking "Schedule now" in the webapp.
17
+
-`SCHEDULER`: The check was run as part of its regular schedule.
18
+
-`TEST_NO_RECORD`: The check triggered from the CLI with `npx checkly test`.
19
+
-`TEST_RECORD`: The check triggered from the CLI with `npx checkly test --record`.
20
+
-`TRIGGER_API`: The check was triggered via the API.
21
+
-`TRIGGER_NO_RECORD`: The check triggered from the CLI with `npx checkly trigger`.
22
+
-`TRIGGER_RECORD`: The check triggered from the CLI with `npx checkly trigger --record`.
23
+
-**CI**: Set to `1` for the following check runs:
24
+
- CLI runs via `npx checkly test` or `npx checkly trigger`.
25
+
- Check runs that are triggered by [deployments](/integrations/ci-cd/github/deployments).
26
+
27
+
The following variables are mostly for informational and debugging purposes and shouldn't be used to influence test behaviour.
28
+
29
+
-`ACCOUNT_ID`: The UUID of the Checkly account as found in the URL.
30
+
-`CHECK_NAME`: The name of the check.
31
+
-`CHECKLY_CHECK_ID`: The UUID of the check as found in the URL.
32
+
-`CHECKLY_REGION`: The region in which the check was executed.
Copy file name to clipboardExpand all lines: platform/variables.mdx
+3-27Lines changed: 3 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,30 +93,6 @@ How variables are accessed depends on where you're accessing them from:
93
93
Handlebar (double brackets) variables will be URI encoded. To avoid encoding, you can access your environment variables with triple brackets, i.e. `{{{VARIABLE_NAME}}}`.
94
94
</Note>
95
95
96
-
## System Variables
97
-
98
-
Checkly provides a set of built-in system variables that you can use in your checks. These variables provide information about the check execution environment, and can be especially useful in playwright checks to distinguish between Checkly executions and local runs.
99
-
100
-
***CHECKLY**: We set this to "1" for all check runs executed by Checkly.
101
-
***CHECKLY_RUN_SOURCE**: This variable indicates the source or reason why the check was run. You can use this to skip parts of your test suite in certain scenarios. Possible values include:
102
-
*`CLI_DEPLOY`: When checks are deployed using `npx checkly deploy` their first run is scheduled with this type.
103
-
*`DEPLOYMENT`: The check was triggered as part of a [CI/CD deployment](/integrations/ci-cd/github/deployments).
104
-
*`EDITOR`: Browser, multi step and API check editor page.
105
-
*`GROUP_RUN_ALL`: Group edit "Run all checks" button.
106
-
*`SCHEDULE_NOW`: The check was triggered manually by a user clicking "Schedule now" in the webapp.
107
-
*`SCHEDULER`: The check was executed as part of its regular schedule.
108
-
*`TEST_NO_RECORD`: CLI `npx checkly test`.
109
-
*`TEST_RECORD`: CLI `npx checkly test --record`.
110
-
*`TRIGGER_API`: The check was triggered via the API.
***CI**: We set this to "1" for the following check runs:
114
-
* CLI runs via `npx checkly test` or `npx checkly trigger`.
115
-
* Check runs that are triggered by [deployments](/integrations/ci-cd/github/deployments).
116
-
117
-
The following variables are mostly for informational and debugging purposes and shouldn't be used to influence test behaviour.
118
-
119
-
*`ACCOUNT_ID`: The UUID of the Checkly account as found in the URL.
120
-
*`CHECK_NAME`: The name of the check.
121
-
*`CHECKLY_CHECK_ID`: The UUID of the check as found in the URL.
122
-
*`CHECKLY_REGION`: The region in which the check was executed.
96
+
## Playwright Check Suite Variables
97
+
98
+
Checkly provides a set of [built-in environment variables](/detect/synthetic-monitoring/playwright-checks/environment-variables) that you can use in your [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) to distinguish between Checkly executions and local runs.
0 commit comments