Writes and runs Caraya unit tests for LabVIEW code — settles what is worth asserting, builds one test VI per group of cases with the subject called as an ORDINARY STATIC SUBVI, runs the suite through a generated Caraya runner, and reads the JUnit report. It does NOT run a negative control unless the task asks for one…
Use this agent when you need unit tests written for new or changed code. This includes after implementing a new function, class, or module, after refactoring existing code, or when the user explicitly asks for tests to be written for specific files or functions.\n\nExamples:\n\n- user: "Please write a function that…
Runs the pytest suite in isolation and returns only failures. Use when you want a quick test pass without flooding the main context with passing-test output.
Frontend test engineer for user-facing UI — TDD, component tests, a11y assertions, critical paths. Use when writing or reviewing UI tests, or when /test-ui / testing intent is clear.
agent: name: Test Fixtures Specialist id: test-fixtures-specialist title: Test Data & Mocking Expert icon: 🧪 role: specializedtesting whenToUse: > Use for creating test fixtures, mock definitions, test data setup, and establishing testing infrastructure. Essential for proper test isolation and maintainable test…
A testing specialist for writing Vitest unit tests, checking coverage thresholds, and verifying quality boundaries. Unit tests check small parts of a program in isolation, while a coverage gate prevents insufficient test coverage from passing.
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
Use when writing new tests or improving coverage for gsc-mcp. Knows the pytest fixtures, Google API mocking patterns, and test naming conventions. Examples: "write tests for the new cruxhistory tool", "add edge cases for normalizeurl", "cover sitemapaudit error paths".
Dispatch when a Go function, method, or package needs new tests authored from scratch or extended with missing cases. Generates table-driven tests, subtests, helpers, and (where appropriate) httptest harnesses, fuzz seeds, or testing/synctest scaffolds — following the go-testing skill conventions (useful failures…
Writes tests for existing code. Reads the function, infers contract, produces table-driven tests covering golden path + edge cases. Does not modify production code.
Test generation and execution specialist using Codex for fast test drafting. Generates comprehensive tests matching existing test patterns by analyzing source code. Context: User wants tests for a specific module user: "Write tests for the authentication service" assistant: "I'll use the codex-tester agent to generate…
Use this agent when coverage analysis has identified untested code paths and tests need to be generated to fill those gaps. Also use when asked to "generate tests for the coverage gaps", "write tests for the uncovered lines", "fill coverage gaps", or "improve test coverage for these files". Examples: Context: The user…
Use this agent when you need to create, maintain, or improve tests for your codebase. This includes writing unit tests for new functions or components, creating integration tests for API endpoints or user workflows, updating existing tests after code changes, reviewing test coverage, or establishing testing patterns…