testing-qa
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
Python testing with pytest framework for unit, integration, and API tests. Use when: (1) Writing test cases for Python code, (2) Setting up pytest fixtures, (3) Testing async functions with pytest-asyncio, (4) Mocking dependencies, (5) Parameterizing tests, (6) Testing FastAPI/Flask endpoints, (7) Setting up test coverage, (8) Creating test factories with factory_boy, (9) Configuring CI/CD test pipelines.
Run tests and analyze failures with actionable fixes. Use when user wants to run tests or debug test failures.
Tests web applications with Playwright including E2E tests, locators, assertions, and visual testing. Use when writing end-to-end tests, testing across browsers, automating user flows, or debugging test failures.
Use TDD workflow (Red-Green-Refactor-Validate) when creating or modifying any business logic, use cases, or domain code. MANDATORY for all implementations. Apply when user requests new features, bug fixes, or refactoring that involves testable code.
Toolkit for interacting with and testing local web programs using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Comprehensive testing guide for Yoto Smart Stream - covering authentication testing, functional testing, Playwright UI automation, and test-and-fix development loops. Use when writing tests, debugging test failures, or implementing test coverage.
End-to-end frontend testing with Playwright Java and Chromium. Use for UI validation, form testing, API interaction verification, and screenshot capture on failures.
Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic.
Test-driven development with independent verification to prevent test gaming. TDD workflows, test generation, coverage validation (≥80% gate, ≥95% target), property-based testing, edge case discovery. Use when implementing TDD workflows, generating comprehensive test suites, validating test coverage, or preventing test gaming through independent multi-agent verification.
Set up and improve WebF app tests with Vitest and React Testing Library. Use when the user mentions Vitest, React Testing Library, unit tests, component tests, “testing trophy”, or asks to add/fix tests in a Vite/React/TS WebF app.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
REQUIRED for ANY interaction with test files (.test.ts, .test.tsx). Use when creating tests, modifying tests, debugging test failures, reviewing test code, refactoring tests, or implementing TDD workflow. Must invoke before writing, reading, or changing any test file.
How to make good playwright (e2e) tests for this project.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Best practices for writing integration tests using Testcontainers and EF Core. Use when creating or modifying integration tests.
Writing unit tests with vitest and vue-test-utils following project patterns. Use when creating tests for components, composables, utilities, or stores.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Run regression testing suite to verify existing functionality still works after changes