Loading...
Loading...
Found 44 Skills
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.
Chai assertion library for JavaScript. Use for JS assertions.
Gatling load testing for APIs. Use for load testing.
Use when writing, reviewing, or debugging Jest + React Testing Library tests, before writing test code or when tests fail
Test web applications comprehensively for quality. Performs functional, integration, and user experience testing of web applications.
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
Used when implementing any feature or bug fix before writing production code
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
Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.
General testing best practices and guidelines for writing comprehensive, maintainable tests across different testing frameworks and languages.
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.
Testing patterns and best practices for unit, integration, and E2E testing.