treido-testing
Testing specialist for Treido (Playwright + Next.js). Use for writing/debugging E2E tests, deflaking, selectors, auth state, parallel execution, and CI stability.
Best use case
treido-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Testing specialist for Treido (Playwright + Next.js). Use for writing/debugging E2E tests, deflaking, selectors, auth state, parallel execution, and CI stability.
Teams using treido-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/treido-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How treido-testing Compares
| Feature / Agent | treido-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Testing specialist for Treido (Playwright + Next.js). Use for writing/debugging E2E tests, deflaking, selectors, auth state, parallel execution, and CI stability.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Playwright + Next.js Testing Best Practices Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests. ## When to Apply Reference these guidelines when: - Writing new Playwright tests for Next.js apps - Debugging flaky or failing tests - Optimizing test execution speed - Setting up authentication state reuse - Configuring CI/CD pipelines for testing - Testing Server Components and App Router features - Reviewing test code for reliability issues ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Test Architecture | CRITICAL | `arch-` | | 2 | Selectors & Locators | CRITICAL | `loc-` | | 3 | Waiting & Assertions | HIGH | `wait-` | | 4 | Authentication & State | HIGH | `auth-` | | 5 | Mocking & Network | MEDIUM-HIGH | `mock-` | | 6 | Next.js Integration | MEDIUM | `next-` | | 7 | Performance & Speed | MEDIUM | `perf-` | | 8 | Debugging & CI | LOW-MEDIUM | `debug-` | ## Quick Reference ### 1. Test Architecture (CRITICAL) - [`arch-test-isolation`](references/arch-test-isolation.md) - Use fresh browser context for each test - [`arch-parallel-execution`](references/arch-parallel-execution.md) - Enable parallel test execution - [`arch-page-object-model`](references/arch-page-object-model.md) - Use Page Object Model for complex pages - [`arch-fixtures`](references/arch-fixtures.md) - Use fixtures for shared setup - [`arch-test-production`](references/arch-test-production.md) - Test against production builds - [`arch-cleanup-state`](references/arch-cleanup-state.md) - Clean up test state after each test ### 2. Selectors & Locators (CRITICAL) - [`loc-role-selectors`](references/loc-role-selectors.md) - Use role-based selectors over CSS - [`loc-data-testid`](references/loc-data-testid.md) - Use data-testid for dynamic elements - [`loc-label-selectors`](references/loc-label-selectors.md) - Use getByLabel for form inputs - [`loc-text-selectors`](references/loc-text-selectors.md) - Use getByText for static content - [`loc-avoid-xpath`](references/loc-avoid-xpath.md) - Avoid XPath selectors - [`loc-chained-locators`](references/loc-chained-locators.md) - Chain locators for specificity - [`loc-placeholder-selector`](references/loc-placeholder-selector.md) - Use getByPlaceholder sparingly ### 3. Waiting & Assertions (HIGH) - [`wait-web-first-assertions`](references/wait-web-first-assertions.md) - Use web-first assertions - [`wait-avoid-hard-waits`](references/wait-avoid-hard-waits.md) - Avoid hard waits - [`wait-network-idle`](references/wait-network-idle.md) - Use network idle for complex pages - [`wait-action-retries`](references/wait-action-retries.md) - Let actions auto-wait before interacting - [`wait-soft-assertions`](references/wait-soft-assertions.md) - Use soft assertions for non-critical checks - [`wait-custom-timeout`](references/wait-custom-timeout.md) - Configure timeouts appropriately ### 4. Authentication & State (HIGH) - [`auth-storage-state`](references/auth-storage-state.md) - Reuse authentication with storage state - [`auth-multiple-roles`](references/auth-multiple-roles.md) - Use separate storage states for different roles - [`auth-session-storage`](references/auth-session-storage.md) - Handle session storage for auth - [`auth-api-login`](references/auth-api-login.md) - Use API login for faster auth setup - [`auth-parallel-workers`](references/auth-parallel-workers.md) - Use worker-scoped auth for parallel tests ### 5. Mocking & Network (MEDIUM-HIGH) - [`mock-api-responses`](references/mock-api-responses.md) - Mock API responses for deterministic tests - [`mock-intercept-modify`](references/mock-intercept-modify.md) - Intercept and modify real responses - [`mock-har-files`](references/mock-har-files.md) - Use HAR files for complex mock scenarios - [`mock-abort-requests`](references/mock-abort-requests.md) - Abort unnecessary requests - [`mock-network-conditions`](references/mock-network-conditions.md) - Simulate network conditions ### 6. Next.js Integration (MEDIUM) - [`next-wait-hydration`](references/next-wait-hydration.md) - Wait for hydration before interacting - [`next-server-components`](references/next-server-components.md) - Test server components correctly - [`next-app-router-navigation`](references/next-app-router-navigation.md) - Test App Router navigation patterns - [`next-server-actions`](references/next-server-actions.md) - Test server actions end-to-end - [`next-baseurl-config`](references/next-baseurl-config.md) - Configure baseURL for clean navigation ### 7. Performance & Speed (MEDIUM) - [`perf-sharding`](references/perf-sharding.md) - Use sharding for large test suites - [`perf-headless-ci`](references/perf-headless-ci.md) - Use headless mode in CI - [`perf-browser-selection`](references/perf-browser-selection.md) - Select browsers strategically - [`perf-reuse-server`](references/perf-reuse-server.md) - Reuse development server when possible - [`perf-retries`](references/perf-retries.md) - Configure retries for flaky test recovery ### 8. Debugging & CI (LOW-MEDIUM) - [`debug-trace-viewer`](references/debug-trace-viewer.md) - Use trace viewer for failed tests - [`debug-screenshots-videos`](references/debug-screenshots-videos.md) - Capture screenshots and videos on failure - [`debug-inspector`](references/debug-inspector.md) - Use Playwright Inspector for interactive debugging - [`debug-ci-reporters`](references/debug-ci-reporters.md) - Configure reporters for CI integration ## How to Use Read individual reference files for detailed explanations and code examples: - [Section definitions](references/_sections.md) - Category structure and impact levels - [Rule template](assets/templates/_template.md) - Template for adding new rules ## Reference Files | File | Description | |------|-------------| | [AGENTS.md](AGENTS.md) | Complete compiled guide with all rules | | [references/_sections.md](references/_sections.md) | Category definitions and ordering | | [assets/templates/_template.md](assets/templates/_template.md) | Template for new rules | | [metadata.json](metadata.json) | Version and reference information |
Related Skills
web-security-testing
Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.
web-app-testing
Gemini 2.5 Computer Use for browser automation with VISIBLE local browser. Watch Gemini AI control your browser in real-time. Perfect for web app testing, automation demos, and debugging.
wallaby-testing
Check test status and debug failing tests using Wallaby.js real-time test results. Use after making code changes to verify tests pass, when checking if tests are failing, debugging test errors, analyzing assertions, inspecting runtime values, checking coverage, updating snapshots, or when user mentions Wallaby, tests, coverage, or test status.
unit-testing-test-generate
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
testing-workflow
Meta-skill that orchestrates comprehensive testing across a project by coordinating testing-patterns, e2e-testing, and testing agents. Use when setting up testing for a new project, improving coverage for an existing project, establishing a testing strategy, or verifying quality before a release.
testing-strategy
Comprehensive guide for implementing AIDB tests following E2E-first philosophy, DebugInterface abstraction, and MCP response health standards
testing-strategies
Testing strategies, patterns, and best practices for production code
testing-services
Writes unit tests for Python service classes using Arrange-Act-Assert pattern with proper mocking at boundaries. Tests behavior, not implementation. Mocks external systems only (API calls, file I/O, databases). Use when writing tests for services or fixing test coverage.
testing-quality
Plans and executes comprehensive testing strategy across frontend, backend, and AI tiers. Activates when writing tests, testing features, setting up test infrastructure, checking coverage, running E2E tests, or performance testing. Does not handle writing production code (backend-developer or frontend-developer), vulnerability/security review (security), or infrastructure deployment (devops).
testing-patterns
Testing patterns using bun:test with in-memory SQLite. Use when writing unit tests, integration tests, or router tests.
testing-obsessive
This skill should be used when the user mentions "write tests", "test coverage", "testing strategy", "unit tests", "integration tests", "e2e tests", "vitest", "jest", discusses testing approaches, asks about test patterns, or works on test files. Addresses testing fundamentals with emphasis on Vitest and Svelte component testing using pragmatic, risk-based approaches.
testing
Comprehensive testing specialization covering test strategy, automation, TDD methodology, test writing, and web app testing. Use when setting up test infrastructure, writing tests, implementing TDD workflows, analyzing coverage, integrating tests into CI/CD, or testing web applications with Playwright. Framework-agnostic approach with framework-specific guidance via reference files.