Loading...
Loading...
Found 43 Skills
ALWAYS use when testing Angular applications with Cypress, E2E testing, or component testing in Angular.
Rstest best practices for config, CLI workflow, test writing, mocking, snapshot testing, DOM testing, coverage, multi-project setup, CI integration, performance and debugging. Use when writing, reviewing, or troubleshooting Rstest test projects.
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.
Design and implement integration tests that verify component interactions, API endpoints, database operations, and external service communication. Use for integration test, API test, end-to-end component testing, and service layer validation.
Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing. Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code.
Specialized skill for .NET unit testing fundamentals and FIRST principles. Use this skill when you need to create unit tests, understand testing fundamentals, learn the 3A Pattern, or master testing best practices. Covers FIRST principles, AAA Pattern, Fact/Theory, test pyramid, etc. Keywords: unit test, unit testing, test fundamentals, FIRST principle, 3A pattern, AAA pattern, Arrange Act Assert, Fact, Theory, InlineData, how to write tests, testing best practices, creating unit tests
Use when vitest performance optimization including fast execution, watch mode, and parallelization strategies.
Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.
Use before claiming work is complete, fixed, or tested; before committing or creating a PR — you must run verification commands and confirm the output before claiming success; always back up assertions with evidence
Test web applications comprehensively for quality. Performs functional, integration, and user experience testing of web applications.
Patterns for using Testcontainers in .NET integration tests to spin up real dependencies like databases and message queues. Use when writing integration tests that require real databases, testing with message brokers like RabbitMQ or Kafka, or isolating test dependencies with Docker containers.
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.