Results for “stateful-testing”

`analysis-agent`/`task-agent`/`review-agent`: use when lifecycle states, transitions, guards, or terminal states need modeling; skip when no state-machine decision exists.

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Analyzes test suites to measure assertion diversity, detect shallow or trivial assertions, and identify tests that lack meaningful verification.

Guides statistical hypothesis testing with assumption checks, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting for research data.

`analysis-agent`/`task-agent`/`review-agent`: use when behavior needs deterministic seams for time, randomness, UUIDs, collaborators, or external I/O; skip when seams are adequate.

`task-agent`: use when local, server, global, derived, optimistic, persisted, form, auth, or cache state ownership changes; skip when state boundaries are unaffected.

Use when creating test scenarios for a skill, setting up a tests/ directory for a plugin or package, running skill tests against a subagent, or verifying whether a SKILL.md changes agent behavior

Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Model complex UI behavior as finite state machines with states, events, and transitions to eliminate impossible states and make behavior predictable.

Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.

Guía para elegir y aplicar tests de hipótesis con SciPy, verificando supuestos, interpretando p-values y tamaño del efecto, y evitando falsos positivos.

Audit datasets for structure, missingness, labeling, suspicious values, duplicate identifiers, and documentation readiness. Use when a researcher asks for data QA, codebook review, sanity checks, or pre-analysis cleanup guidance.