Specialized agent for comprehensive testing of the BarqNet project across all platforms and layers. Handles unit testing, integration testing, E2E testing, performance testing, security testing, and test automation. Creates test plans, writes test code, executes tests, and generates test reports. Use when implementing tests, debugging test failures, or validating functionality.
Run comprehensive quality verification on workshop or demo content using Red Hat standards and validation agents.
⚠️ MANDATORY - Automatically invoked by safe-commit. Executes comprehensive testing suite including unit tests (minimum 90% coverage), integration tests, and E2E tests (100% pass required). Reports coverage and failures. MUST pass before commit. NEVER run tests manually before commit.
Analisa commits e sugere testes necessários (unit, integration, contract, smoke, E2E). Roda em background após commits.
This skill should be used when the user asks to "write tests", "add unit tests", "create test cases", "test this function", "add test coverage", or discusses testing strategies and test implementation.
Comprehensive pytest testing skill for Python projects with specialized FastAPI support. Use when: (1) User wants to generate test files for existing code, (2) User asks about pytest patterns, best practices, fixtures, or test organization, (3) User is working with FastAPI testing (TestClient, async tests, dependency overrides, authentication), (4) User needs help writing tests, configuring pytest, or organizing test suites. Includes test generation script, FastAPI-specific patterns, fixture templates, and comprehensive pytest reference documentation.
Verifies API documentation against source code to eliminate fabricated claims, ensure accuracy, and validate examples. Zero tolerance for unverified claims, marketing language, or non-runnable code examples. Use before committing API docs or during documentation reviews.
Testing and quality validation for Flutter code. USE WHEN: creating tests, verifying coverage, running E2E tests, validating code quality, checking test coverage thresholds. Minimum coverage: 80% overall, 95% services, 70% widgets. Examples: <example> Context: The user implemented a new feature. user: "I've just implemented the new itinerary creation service" assistant: "I'll use testing-agent to generate comprehensive tests and ensure quality." <commentary>New code needs testing - use testing-agent.</commentary> </example> <example> Context: The user wants to run E2E tests. user: "Run the E2E tests to validate the login flow" assistant: "I'll use testing-agent to execute E2E tests with MCP Chrome DevTools." <commentary>E2E testing is a testing-agent responsibility.</commentary> </example>
Review Vitest configuration for deprecated patterns and best practices. Use when reviewing test configuration or vitest setup.
Automatically diagnose and fix failing tests by analyzing errors, updating assertions, and refactoring test code
Reviews test quality against guidelines/tests.md standards for TypeScript/Node.js projects
Review code for Playwright Guidelines compliance. Use when asked to "review my playwright tests", "check accessibility", or "check my tests against best practices".
Use this skill when integrating an external Go project with consent testing utilities. Triggers include testing authenticated routes, setting up dev mode login, writing tests for authorization, using TestVerifier, creating authenticated test requests, or local development without a real consent server.
Use when Codex must browse, interact with, or test web flows via the remote Playwright MCP server hosted on Glama.
Write and manage tests using TDD with Pest (PHP), Vitest (React), pytest (Python), and Playwright (E2E). Use when writing feature tests, unit tests, component tests, visual regression tests, or improving test coverage. EXCLUSIVE to testing-expert agent.
Iterate on UI visuals by editing code, hot reloading, capturing screenshots, and refining in loops.
后端测试开发规范。强调函数式测试优先，详细说明了 fixtures 的使用、pytest markers 的分类约定以及数据库隔离策略。
Writing high-quality unit tests for JavaScript and TypeScript using Jest. Covers test structure (AAA pattern, USE naming), breaking dependencies (stubs, mocks, dependency injection), testing async code (promises, callbacks, timers), avoiding flaky tests, and test-driven development. Use when writing tests, debugging test failures, refactoring tests for maintainability, or questions about Jest, TDD, mocks, stubs, or test best practices.
Write comprehensive Vitest tests for TypeScript and React. Use when creating unit tests, component tests, improving test coverage, or when user asks about testing patterns, mocking, or test utilities.
