clerk-testing

Configure Clerk authentication state for Playwright and Cypress end-to-end tests.

18|Updated Jul 23, 2025
One-click install
npx skills add https://github.com/faw01/create-mf2-app --skill clerk-testing-faw01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-testing
Source: https://github.com/faw01/create-mf2-app/tree/main/apps/cli/template/.agents/skills/clerk-testing
Command: npx skills add https://github.com/faw01/create-mf2-app --skill clerk-testing-faw01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of testing authentication flows in Clerk-integrated applications by providing a standardized approach to session management and environment setup.

Core Features & Use Cases

  • Isolated Auth State: Ensures each test runs with a fresh, isolated session to prevent state leakage.
  • Environment Bypassing: Provides utilities to bypass bot detection and initialize testing tokens efficiently.
  • Use Case: When running a suite of Playwright or Cypress tests for a SaaS platform, use this Skill to configure global setup and storage states, ensuring your auth-protected routes are tested reliably without manual sign-in overhead.

Quick Start

Use the clerk-testing skill to configure the global setup for your Playwright test suite using the required testing token.

Frequently Asked Questions about clerk-testing

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

FAQPage Schema
How do I handle Clerk authentication state in Playwright E2E tests?

To bypass bot detection in Clerk E2E testing, you use provided environment utilities to initialize testing tokens efficiently. This ensures secure and isolated test execution for your Cypress or Playwright suites without triggering security blocks.

Can I use Cypress to test auth-protected routes in a Clerk-enabled application?

To configure Clerk testing tokens for E2E tests, you set up environment-specific configurations using valid Clerk testing tokens. This automates session management and bot detection bypass for secure, isolated test execution.

Why does my Clerk authentication state leak between E2E test runs?

To automate Clerk session setup for E2E tests, you configure global setup scripts using required testing tokens. This handles session persistence and bot detection bypass, eliminating manual sign-in overhead for auth-protected routes.

What is the best way to automate Clerk sign-in for E2E testing?

The best way to automate Clerk sign-in for E2E testing is using a standardized approach to session management. This skill configures global setup and storage states, eliminating manual sign-in overhead for auth-protected routes.

Do I need a testing token to run Playwright tests with Clerk?

Yes, you need a valid Clerk testing token to run Playwright tests. The token is required to configure the global setup, initialize environment bypassing, and ensure secure, isolated test execution for your application.