Native Playwright tests
Use @playwright/test imports, fixtures, hooks, locators, and assertions. Relative navigation uses the monitored service URL.
Browser journeys
Run the browser tests your users depend on.
Execute native Playwright JavaScript and TypeScript scripts through the Telesis CLI or MCP. Use assertions, login flows, and failure evidence in a bounded Docker sandbox.
Playwright Monitoring
Browser journeys
What Telesis inspects
- Native Playwright tests
- Authenticated local journeys
- Actionable test evidence
- Bounded execution
What you get
Authenticated local journeys
Inject named secrets or reuse a private session file locally. Result text redacts literal secrets; authenticated recordings require explicit opt-in.
Actionable test evidence
Inspect test outcomes, script revisions, bounded console logs, screenshots, and optional video and traces in a private local report.
Bounded execution
One worker, no retries, a 120-second cap, resource limits, and container cleanup on cancellation. Scheduled use requires a compatible runner.
Why teams pick it
- The same scripts run from CLI and MCP
- Nonzero CLI exits for unsuccessful checks
- Docker and image readiness exposed by doctor
- Local login secrets stay out of saved monitor definitions
Ready to try Playwright Monitoring?
Execute native Playwright JavaScript and TypeScript scripts through the Telesis CLI or MCP. Use assertions, login flows, and failure evidence in a bounded Docker sandbox.