Results for “regression-test”

Develop, test, and document UI components in isolation with Storybook, including interactive controls, accessibility testing, and visual regression.

Runs and writes tests for a project, supporting unit, integration, and end-to-end scopes, plus two-pass TDD orchestration with quality-gate checks and regression sweeps.

Sets up and runs end-to-end tests with Playwright, including browser automation, visual regression, cross-browser testing, and CI/CD integration.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Run static BSP checks and on-target smoke/regression tests on a flashed NVIDIA Jetson device to validate a customized BSP image.

Automates git bisect workflows with custom test scripts and CI pipeline integration to identify regression-introducing commits.

Diagnose bugs by establishing a tight feedback loop, tracing root cause, and verifying fixes with regression tests before making changes.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Expert en tests d'agents IA (tests unitaires, intégration, régression, guardrails, red teaming agents)

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

`analysis-agent`/`task-agent`/`review-agent`: use for recurrence guards on known defects, incidents, or escaped failures; skip speculative risk without a prior failure mechanism.

Build evaluation frameworks for agent systems with deterministic checks, regression suites, multi-dimensional rubrics, quality gates, production monitoring, and outcome measurement.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Rehearse

Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.

Use when making changes to existing systems to ensure those changes don't break existing functionality. This skill provides procedures for identifying at-risk areas, adding regression tests, and validating changes don't cause unintended side effects.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.

LLM output evaluation — automated metrics, LLM-as-judge, A/B testing, regression testing. Use when measuring LLM output quality, comparing prompt or model versions, building an automated eval pipeline, setting up regression tests for prompt changes, or evaluating RAG systems and bias/safety.

Design and evaluate A/B tests with power, sample size, and robust metric interpretation. Use when: (1) planning controlled experiments, (2) reading p-values/effects, (3) sequential testing safeguards. NOT for: dark-pattern optimization.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

proptest — property-based testing for Rust (Hypothesis-style). Generates thousands of random inputs to find counterexamples to invariants, with shrinking to minimal failing case. Critical for crypto, parsers, state machines, and finance code where edge cases matter. Includes strategies (gen functions), regression tracking, and integration with cargo test. Alternative: quickcheck (simpler API, less powerful). USE WHEN: user mentions "proptest", "property-based test", "proptest!", "Strategy", "Arbitrary", "shrink", "quickcheck", "regression file", "fuzz-light", "proptest-derive" DO NOT USE FOR: Generic Rust unit tests - use `testing/rust-testing` DO NOT USE FOR: Fuzzing with mutator (cargo-fuzz, AFL) - use bitcoin/testing/fuzz DO NOT USE FOR: KMP property testing - use `testing/kotest` (has built-in property)

Evaluates machine-generated log summaries without human-written references, using LLM judgment and dense embeddings to score relevance, informativeness, and coherence.

Designs and executes load tests, covering scenario design, baseline capture, execution configuration, results analysis, and reporting for k6, Locust, Gatling, and JMeter.

Use this skill for reproduction-first debugging, root cause isolation, minimal fixes, regression tests. Trigger when the task involves agent profile work related to Staff Debugger Agent, implementation, audits, debugging, strategy, or validation.

`analysis-agent`/`task-agent`/`review-agent`: use when logic, rules, invariants, branches, edges, or failure paths need isolated tests; skip without a unit-test decision.

Performance regression detection using the browse daemon. (gstack)

Runs and writes tests, verifies behavior, and orchestrates two-pass TDD across scoped modes, blocking on quality gates and never editing production code.

Comprehensive results analysis for empirical research: generate publication-quality descriptive statistics and balance tables, interpret regression coefficients with economic magnitude and effect sizes, assess identification assumption diagnostics, and produce structured results memos. Use when asked to create summary statistics, Table 1, balance tests, interpret results, assess economic significance, or write results narratives.