Results for “test”

Provides Playwright patterns for building stable, fast, and maintainable E2E test suites, including Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Write and organize F# tests using xUnit, FsUnit, Unquote, FsCheck for property-based testing, and integration test patterns with ASP.NET Core and Testcontainers.

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...

Validates API endpoints, performs contract and integration testing, documents issues, and assesses performance and reliability.

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

Agent skill for tester - invoke with $agent-tester

This skill should be used when the user asks to "improve test coverage", "add unit tests", "TDD", "test this module", "write tests for", "increase coverage", "/ut command", or discusses unit testing strategies. Covers the unit test loop workflow, React Testing Library best practices, query priorities, and coverage improvement strategies.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, or refactoring.

Provides a structured workflow for unit, integration, E2E, and performance testing, including browser automation, code review, and quality gates.

Analyzes production code to find gaps in existing tests by reasoning about hypothetical mutations and checking whether tests would catch them.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, and refactoring.

Refactors test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, and mocking strategy, removing implementation-detail or low-value tests.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests when writing features, fixing bugs, or refactoring code.

Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.

Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking dependencies, or setting up test infrastructure. Don't use for E2E testing with Cypress or Playwright, or for testing non-Angular JavaScript/TypeScript code.

Write effective unit tests with TUnit, covering standard tests, data-driven tests, and migration from xUnit.

Runs a complete testing pipeline covering full test suites, automated and manual tests, and logs execution metadata for the /evolve pipeline.

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.

Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"

Jest testing framework. Covers unit tests, mocking, and snapshots. Use for testing React and Node.js projects. USE WHEN: user mentions "jest", "jest test", "snapshot test", asks about "jest.fn", "jest.mock", "toMatchSnapshot", "React testing" DO NOT USE FOR: E2E tests - use `playwright` or `cypress`; Vite projects - use `vitest` instead; React component testing alone - combine with `testing-library`

This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Analyzes test suites across multiple languages and tags each test with standardized traits (positive, negative, critical-path, etc.) for better test categorization and coverage visibility.

Runs AI-powered exploratory testing on web applications using the ScoutQA CLI, including smoke tests, accessibility audits, and user flow validation.

Guides implementing features and bug fixes test-first, enforcing red-green-refactor with mandatory failure verification.

Plan and execute game QA including functional testing, playtesting, performance testing, compatibility testing, and bug tracking workflows. Use when setting up quality assurance for a game project. Also trigger for "game QA", "playtest", "bug tracking", "game testing", "QA plan", "regression testing", or "compatibility testing".

Generates unit tests, integration tests, and E2E tests for React/Next.js applications by scanning components, analyzing coverage reports, and scaffolding Playwright test files.

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Skill Tester

Skill Tester

Cpp Testing

Generate api test generator operations. Auto-activating skill for Test Automation. Triggers on: api test generator, api test generator Part of the Test Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like "api test generator", "api generator", "api".

AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.