Unit Testing

Test-Driven Development for Rust. Use when creating new functionality, writing tests, or fixing bugs through the Red-Green-Refactor TDD cycle.

Use when working on the Miden compiler (`midenc` / `cargo miden`), debugging failing tests or implementing compiler changes, and you need a Miden VM MASM execution trace to understand the stack state after each instruction. Covers `MIDENC_TRACE=executor=trace` (typically with `cargo make test -- --no-capture ...`).

Automatically wraps verbose commands (pytest, ruff, builds) with silent execution for context-efficient output. Use this proactively when running tests, linters, formatters, or build commands to minimize context usage while preserving error information.

Sensitive data patterns for security testing: API keys, credit cards, emails, SSNs, phone numbers, IPs, and more. Use for data discovery and validation.

Execute tests from persistent test cases. Reads ./tests/ directory, runs cleanup, wallet setup (if Web3), executes tests, and generates report.

Execute shell commands in persistent, stateful VT100 terminal sessions. WHEN: User needs to "run a command", "execute shell", "build project", "run tests", "deploy", system administration. WHEN NOT: Simple file operations (use fs_* tools), reading known files (use fs_read_file).

Comprehensive guidance for writing high-quality unit tests in Java projects using JUnit 5 and AssertJ. Use when writing unit tests, creating test classes, or need guidance on mocking strategies, assertions, test builders, or JUnit 5 best practices. Requires JUnit 5, AssertJ, and Mockito dependencies.

Yeni özellikler geliştirirken mimari uyum, performans etkileri ve best practices önerileri sunar. İstekte bulunduğunuzda özellikleri implement eder ve testlerini yazar.

Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales

Generate pytest test templates for UTXOracle modules following TDD patterns. Automatically creates RED phase tests with async fixtures, coverage markers, and integration test stubs.

Write E2E tests using Playwright with Cucumber/Gherkin for this project. Use when creating tests, writing test cases, testing UI flows, API testing, or when user mentions e2e, playwright, cucumber, gherkin, bdd, test automation, or QA.

Verify tests by following recorded trajectories in tests-in-verification.json. Use this skill during the verify stage to independently confirm test results by re-executing recorded steps.

Clean Architecture and Cosmic Python guidance for well-tested, layered Python systems. Use for designing Python projects with layered architecture (models, adapters, services, entrypoints), enforcing Clean Code and SOLID principles, testing strategies (unit tests, BDD, Gherkin), CI/CD setup (pytest, tox, importlinter), and architectural decision-making (ADRs). Applicable to systems requiring strict boundary enforcement, clean separation of concerns, and comprehensive test coverage.

Use PROACTIVELY when auditing code quality, running security scans, assessing technical debt, reviewing code for production readiness, setting up CI quality gates, or tracking DORA metrics. Analyzes codebases against OWASP Top 10, SOLID principles, Testing Trophy, and 2024-25 SDLC standards. Supports incremental audits for large codebases. Not for runtime profiling or real-time monitoring.

Diagnose and repair selftest failures by running diagnostic commands and proposing fixes

Test-first development strategy for PAI projects. USE WHEN user needs test strategy, coverage analysis, ATDD workflows, risk-based testing, or quality gates. Ensures tests are written before code, not after bugs appear.

Design production-grade Terraform modules for home lab infrastructure with HA patterns, proper structure, variable design, and Proxmox optimization. Use when creating new modules, implementing multi-master Kubernetes clusters, load balancers, or building reusable infrastructure components. Includes module structure, HA implementations, cost optimization, and testing patterns.

Enforces zero-tolerance test quality through two-phase testing strategy (Focus → Stable → Regression). Proactively activates when testing context detected. Blocks failures, enforces coverage thresholds (70% min, 85% actors, 80% business logic), and provides gamified feedback. Implements "testing is art in efficiency" - fast module feedback then comprehensive regression.

Reference and maintain consistency with the project's technical stack including frameworks, runtimes, languages, frontend libraries, databases, ORMs, testing tools, deployment platforms, and third-party services. Use this skill when making technology choices or selecting libraries that need to align with the existing stack, adding new dependencies to package.json, pnpm-workspace.yaml, requirements.txt, or other dependency management files, implementing features using the project's established frameworks, ORMs, databases, or APIs, writing code in the project's primary language and runtime environment, setting up testing infrastructure with the project's test frameworks, configuring CI/CD pipelines or deployment settings, integrating third-party services that match the project's existing integrations, ensuring compatibility with the project's build tools and bundlers, or ensuring any technical implementation decision aligns with the project's established technologies, architectural patterns, and conventions doc

테스트 실행 및 품질 검증. Use when:(1) 테스트 실행 요청, (2) 변경 후 검증 필요,(3) 커버리지 확인, (4) CI 전 로컬 검증.