clerk-testing

Set up Playwright or Cypress end-to-end tests for Clerk authentication flows.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/sheriax/drawink --skill clerk-testing-sheriax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-testing
Source: https://github.com/sheriax/drawink/tree/main/.agents/skills/clerk-testing
Command: npx skills add https://github.com/sheriax/drawink --skill clerk-testing-sheriax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of end-to-end testing for applications using Clerk for authentication, ensuring your auth flows are robust and reliable.

Core Features & Use Cases

  • Auth Flow Testing: Write end-to-end tests for user sign-up, sign-in, and other authentication-related flows.
  • Framework Integration: Supports popular testing frameworks like Playwright and Cypress.
  • Use Case: You've just implemented Clerk authentication in your React app. Use this Skill to write Playwright tests that verify a user can successfully sign up, sign in, and access protected routes.

Quick Start

Use the clerk-testing skill to set up Playwright for testing Clerk authentication flows.

Frequently Asked Questions about clerk-testing

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

FAQPage Schema
How do I test Clerk authentication flows with Playwright?▼

You can write end-to-end tests for Clerk authentication by integrating Playwright and utilizing specific setup functions like `clerkSetup()` and `setupClerkTestingToken()` for isolated session management and bot detection bypass.

Can I use Cypress for end-to-end testing of Clerk authentication?▼

Yes, Cypress is supported for end-to-end Clerk authentication testing. You can automate user sign-up, sign-in, and protected route access scenarios using setup functions to handle isolated session management and bypass bot detection.

What is `setupClerkTestingToken` used for in e2e testing?▼

`setupClerkTestingToken` is used for isolated session management and bypassing bot detection during end-to-end testing. It ensures your automated Playwright or Cypress scenarios execute without being blocked by Clerk's security mechanisms.

Why does my automated test fail when signing in with Clerk?▼

Automated Clerk sign-in tests often fail due to triggered bot detection. Implementing `setupClerkTestingToken()` bypasses bot detection and ensures reliable isolated session management during your end-to-end test runs.

How do I verify access to protected routes after Clerk sign-in?▼

You verify protected route access by writing end-to-end tests that simulate user sign-in and then attempt navigation to restricted areas. This skill provides the necessary setup to ensure authentication state is managed correctly throughout the test scenario.