clerk-testing

Automate Clerk authentication flow testing with Playwright or Cypress.

Updated Aug 23, 2026

Search Tags:#playwright #cypress #e2e-testing #clerk #token-management #auth-flow #storage-state

Ready to run

npx skills add https://github.com/awfixers-stuff/opencode-config --skill clerk-testing-awfixers-stuff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clerk-testing
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/clerk-testing
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill clerk-testing-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E testing for Clerk apps, enabling automated authentication flow validation across frameworks. Use with Playwright or Cypress to verify the Clerk auth flow in your CI and local environments.

Core Features & Use Cases

E2E test setup and execution for Clerk apps using Playwright or Cypress
Manage isolated auth state across tests with storageState
Bypass bot detection with clerkSetup and setupClerkTestingToken for reliable tests
Validate Clerk UI presence using selectors like page.waitForSelector('[data-clerk-component]')

Quick Start

Create a Playwright or Cypress test suite that authenticates Clerk users and asserts token issuance and UI rendering

Frequently Asked Questions about clerk-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Clerk authentication flow testing with Playwright?▼

Automate Clerk authentication flow testing by configuring a Playwright test suite with clerkSetup and setupClerkTestingToken to manage tokens and persist authenticated storageState across test runs.

Does Cypress support Clerk E2E testing with persisted auth state?▼

Cypress supports Clerk E2E testing by utilizing setupClerkTestingToken to bypass bot detection and persisting authenticated storageState across isolated test environments and local CI pipelines.

Why does my Clerk E2E test fail due to bot detection?▼

Clerk E2E tests fail due to bot detection when testing tokens are missing; use setupClerkTestingToken and clerkSetup to bypass detection and reliably validate the authentication flow.

How do I validate Clerk UI components during an E2E auth flow test?▼

Validate Clerk UI components during E2E auth flow tests by asserting token issuance and using selectors like page.waitForSelector('[data-clerk-component]') to verify UI rendering.

Can I manage isolated Clerk auth state across different testing environments?▼

Manage isolated Clerk auth state across environments by using storageState persistence in Playwright or Cypress, ensuring token management remains valid in both local and CI pipelines.