“Testing”

Create, repair, and evaluate tests for unit, integration, end-to-end, contract, regression, CI, and bug-fix workflows.

Testing doctrine, pyramid (unit, integration, API, security, smoke), AAA pattern, and coverage enforcement.

Run tests and checks in the sandbox, read the failures and report what passes and what does not.

Test abstractions, not hardware — discovery, capabilities, NAT/firewall generation, cleanup, rollback, uplink switching.

Bun and ghostapi tests.

Use when adding, repairing, selecting, or running tests for a behavior change.

Verify changes with focused, reproducible tests and checks.

Create functional, negative, regression, integration, E2E and security-focused tests for AI-generated applications.

Unified testing commands and patterns across frontend and backend.

Add, update, or diagnose pytest coverage for RLM behavior using focused fake environments and optional Docker integration tests.

Define unit, integration, E2E, visual regression, interaction, and animation-state tests.

Test runner configuration, assertions, and mock structures for smart contracts.

Use for verification strategy, secrets handling, and any future automated tests.

Testing strategy, patterns, and execution conventions

Guidelines for determining how to test a project based on its contents.

Use when deciding how to verify code changes or diagnose test failures.

Guide for testing practices and frameworks

测试驱动的改动流程：先写一条会红的测试，再小步改实现，最后跑目标测试与全量回归并对比基线。

Build and maintain a complete test strategy across unit, integration, and end2end scopes.

Build and maintain a complete test strategy across unit, integration, and end-to-end scopes for the Go service.

Use when deciding what evidence can expose a credible software fault.

Use for XCTest targets, DVR, and CI config secrets in contentstack-swift.

Use when verifying an incident fix and reporting its results.

Red-green-refactor as the default for real feature and bug-fix work; use verification-first when behavior is already clear.