micsapp Clerk CI Integration
Overview
Set up CI/CD pipelines with Clerk authentication testing.
Prerequisites
- GitHub repository with Actions enabled
- Clerk test API keys
- npm/pnpm project configured
Instructions
- Step 1: GitHub Actions Workflow
- Step 2: E2E Testing with Playwright
- Step 3: Test User Setup
- Step 4: Playwright Test Configuration
- Step 5: Authentication Test Helpers
- Step 6: Sample E2E Tests
For full implementation details and code examples, load:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Output
- GitHub Actions workflows configured
- E2E tests with Playwright
- Test user management
- CI/CD pipeline ready
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Secret not found | Missing GitHub secret | Add secret in repo settings |
| Test user not found | User not created | Run setup script first |
| Timeout on sign-in | Slow response | Increase timeout, check network |
| Build fails | Missing env vars | Check all NEXT_PUBLIC vars set |
Resources
Next Steps
Proceed to clerk-deploy-integration for deployment platform setup.
Examples
Basic usage: Apply clerk ci integration to a standard project setup with default configuration options.
Advanced scenario: Customize clerk ci integration for production environments with multiple constraints and team-specific requirements.