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
Copy file name to clipboardExpand all lines: detect/synthetic-monitoring/playwright-checks/configuration.mdx
+82-5Lines changed: 82 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,25 +198,102 @@ The `npx checkly test` command runs your Playwright tests locally using the same
198
198
199
199
### Configuration errors
200
200
201
-
**Invalid `logicalId`**
201
+
#### Invalid `logicalId`
202
202
203
203
```
204
204
Error: logicalId must be unique across all checks
205
205
```
206
206
207
207
Ensure each Playwright Check Suite has a unique `logicalId`. The `logicalId` is used as a stable reference across deployments.
208
208
209
-
**Missing Playwright configuration**
209
+
#### Missing Playwright configuration
210
210
211
211
```
212
212
Error: Cannot find playwright.config.ts at path: ./playwright.config.ts
213
213
```
214
214
215
215
Verify that `playwrightConfigPath` points to the correct relative path from your `checkly.config.ts` file.
216
216
217
+
### Alert optimization
218
+
219
+
#### Alerts are triggered too late
220
+
221
+
Playwright Check Suites wait for `npx playwright test` to finish before triggering an alert on test failure. Use [Playwright's `maxFailures` option](https://playwright.dev/docs/api/class-testconfig#test-config-max-failures) to stop the test run and trigger alerts earlier. This setting halts the entire suite after reaching the specified number of failures, allowing you to receive alerts faster.
222
+
223
+
Specify this option in your `playwright.config` or the `testCommand` in your `checkly.config`.
224
+
225
+
<Tabs>
226
+
<Tabtitle="playwright.config.ts">
227
+
```typescript playwright.config.ts highlight={5}
228
+
import { defineConfig } from'@playwright/test';
229
+
230
+
exportdefaultdefineConfig({
231
+
// Setting to zero (default) disables max failures.
232
+
maxFailures: process.env.CHECKLY==='1'?1:0,
233
+
})
234
+
```
235
+
</Tab>
236
+
<Tabtitle="checkly.config.ts">
237
+
```typescript checkly.config.ts highlight={11}
238
+
import { defineConfig } from'checkly'
239
+
240
+
exportdefaultdefineConfig({
241
+
checks: {
242
+
playwrightConfigPath: './playwright.config.ts',
243
+
playwrightChecks: [
244
+
{
245
+
name: 'E2E test suite',
246
+
logicalId: 'e2e-test-suite',
247
+
pwTags: '@e2e',
248
+
testCommand: 'npx playwright test --max-failures=1',
249
+
}
250
+
]
251
+
},
252
+
})
253
+
```
254
+
</Tab>
255
+
</Tabs>
256
+
257
+
#### Alerts are triggered too often
258
+
259
+
End-to-end testing for complex or flaky applications can be difficult. While it's best if your Playwright tests are not flaky, you can use the [`retries` option](https://playwright.dev/docs/test-retries#retries) to automatically rerun failed tests and prevent false alarms in your Playwright Check Suites monitoring.
260
+
261
+
Specify this option in your `playwright.config` or the `testCommand` in your `checkly.config`.
262
+
263
+
<Tabs>
264
+
<Tabtitle="playwright.config.ts">
265
+
```typescript playwright.config.ts highlight={4}
266
+
import { defineConfig } from'@playwright/test';
267
+
268
+
exportdefaultdefineConfig({
269
+
retries: process.env.CHECKLY==='1'?3:0,
270
+
})
271
+
```
272
+
</Tab>
273
+
<Tabtitle="checkly.config.ts">
274
+
```typescript checkly.config.ts highlight={11}
275
+
import { defineConfig } from'checkly'
276
+
277
+
exportdefaultdefineConfig({
278
+
checks: {
279
+
playwrightConfigPath: './playwright.config.ts',
280
+
playwrightChecks: [
281
+
{
282
+
name: 'E2E test suite',
283
+
logicalId: 'e2e-test-suite',
284
+
pwTags: '@e2e',
285
+
testCommand: 'npx playwright test --retries=3',
286
+
}
287
+
]
288
+
},
289
+
})
290
+
```
291
+
</Tab>
292
+
</Tabs>
293
+
217
294
### Test execution issues
218
295
219
-
**Tests exceed 30-minute limit**
296
+
#### Tests exceed 30-minute limit
220
297
221
298
If your Playwright Check Suite times out after 30 minutes:
222
299
@@ -225,15 +302,15 @@ If your Playwright Check Suite times out after 30 minutes:
225
302
- Optimize slow tests by reducing wait times and parallelizing where possible
226
303
-[Contact Checkly support](https://app.checklyhq.com/?support=true) if you need further help
227
304
228
-
**Dependency installation failures**
305
+
#### Dependency installation failures
229
306
230
307
If dependencies fail to install:
231
308
232
309
- Check that your `package.json` and lock file (e.g., `package-lock.json`) are both included in your deployment.
233
310
- Verify that the private registry authentication is configured correctly. See the [custom dependencies guide](/detect/synthetic-monitoring/playwright-checks/custom-dependencies/) for more details.
234
311
- Adjust the `installCommand` to match your project's expectation.
**Playwright Check Suites turn your Playwright end-to-end tests into production monitors.** Run entire test suites, specific projects, or tagged tests globally without modifying your existing code or configuration.
11
11
12
12
<Warning>
13
-
**Known limitations**: Playwright Check Suites do not currently support monorepo workspaces for dependency installation.
14
-
Each check run has a maximum execution time of 30 minutes.
13
+
**Known limitations**: Each check run has a maximum execution time of 30 minutes.
Copy file name to clipboardExpand all lines: detect/testing/playwright-reporter-changelog.mdx
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,23 @@ Learn more about:
13
13
14
14
## Full release history
15
15
16
+
<Updatelabel="v1.5.0"tags={["February 2026"]}>
17
+
**Added**
18
+
19
+
-**Test command** - The test command is now automatically detected and shown in the Checkly UI. Override with the `testCommand` option or `CHECKLY_TEST_COMMAND` env var.
20
+
-**Job logs** - CI job logs are now included in test session uploads.
21
+
</Update>
22
+
23
+
<Updatelabel="v1.4.2"tags={["February 2026"]}>
24
+
**Fixed**
25
+
26
+
- Missing credentials now show a clean warning instead of a stack trace. Other reporters continue working normally.
Copy file name to clipboardExpand all lines: detect/uptime-monitoring/heartbeat-monitors/overview.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,6 +78,8 @@ Heartbeat monitors provide different metrics and insights than other types of ch
78
78
-**Alert Timeline**: When alerts were triggered and resolved
79
79
-**Source Tracking**: Which systems or processes sent pings
80
80
81
+
Heartbeat metrics are also available via the [Prometheus V2 integration](/integrations/observability/prometheus-v2#heartbeat-metrics), including dead man's switch gauges for alerting in Grafana when a ping is overdue.
82
+
81
83
<Warning>
82
84
Remember: Heartbeat monitors detect when jobs fail to complete, but they can't tell you why a job failed. Combine heartbeat monitoring with application logging and error tracking for complete observability.
0 commit comments