How does this skill help speed up my test suite?

It implements patterns for storageState and globalSetup, allowing you to reuse authentication states across tests instead of signing in manually for every test case.

How do I handle bot detection during automated Clerk tests?

The skill guides you to use the setupClerkTestingToken() function before navigation to ensure your test runner bypasses Clerk's security filters.

Does this skill support both Playwright and Cypress?

Yes, the skill provides specific decision trees and implementation workflows for both Playwright and Cypress frameworks.

Can I use production API keys for testing?

No, it is a recommended best practice to strictly use pk_test and sk_test keys to ensure security and environment isolation.

Clerk E2E Testing

Name: Clerk E2E Testing
Author: clerk

byclerk

•

Security & Testing

Streamlines end-to-end testing for Clerk-powered applications by providing framework-specific guidance for Playwright and Cypress.

This skill equips Claude with the specialized knowledge to implement robust end-to-end testing for Clerk-authenticated applications. It provides a structured workflow for configuring Playwright and Cypress, including the use of testing tokens to bypass bot detection, managing isolated session states, and optimizing performance through storage state persistence. By following the integrated mental model and best practices, developers can ensure their authentication flows are secure and reliable while maintaining fast test execution times by avoiding repetitive UI-based sign-in processes.