Skip to content
AI & Agents
Agent

testing-playwright

Use the command format:

From plugin
caldiy
47k95 skills95 agents
Install
$ npx -y skills add calcom/cal.com --agent claude-code

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Use the command format:

Agent definition

testing-playwright.md
paths:
  - "apps/web/playwright/**"
  - "packages/embeds/**/playwright/**"
  - "apps/**/*.e2e.ts"
  - "apps/api/**/e2e/**"
title: Playwright E2E Testing
impact: HIGH
impactDescription: E2E tests catch integration issues before production
tags: testing, playwright, e2e

Playwright E2E Testing

Running Tests

Use the command format:

PLAYWRIGHT_HEADLESS=1 yarn e2e [test-file.e2e.ts]

This format includes the proper timezone setting, virtual display server, and uses the repository's e2e runner.

**Do not use** the standard `yarn playwright test` command.

Local Testing First

Always ensure Playwright tests pass locally before pushing code. The user requires fast local e2e feedback loops instead of relying on CI, which is too slow for development iteration.

**Never push test code until those tests are passing locally first.**

CI Behavior

  • E2E tests will only run if PR has "ready-for-e2e" label
  • When E2E tests are skipped, the "required" check intentionally fails to prevent merging without E2E
  • Do not try to fix anything related to skipped E2E tests - this is expected behavior
Ships withcaldiy

Scheduling infrastructure for absolutely everyone.

Get the whole plugin