What problem does it solve?
It removes flaky, slow, and inconsistent end-to-end testing of Clerk authentication by ensuring each test runs with a fresh and valid Clerk auth context.
Core Features & Use Cases
- Decision-ready framework selection: Choose Playwright or Cypress and follow the matching official testing path for Clerk.
- Deterministic auth initialization: Initialize the Clerk testing environment with
clerkSetup() and set up setupClerkTestingToken() before visiting auth pages.
- Fast, reusable authenticated sessions: Use
storageState to persist auth between tests and avoid repeating UI-based sign-in for every run.
- Secure test credentials: Use only
pk_test_* and sk_test_* keys to avoid production key leakage.
- Framework-specific wiring: Use Playwright
globalSetup for auth state or add Cypress commands via addClerkCommands({ Cypress, cy }) for file support.
Quick Start
Ask the skill to guide you through setting up Playwright-based Clerk auth E2E tests using your Clerk CLERK_TESTING_TOKEN and pk_test_*/sk_test_* keys, saving authenticated state with storageState.