tests-performance

Audits test suite speed and runner configuration to produce an impact-ranked optimization plan.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill tests-performance-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests-performance
Source: https://github.com/greglas75/zuvo/tree/main/skills/tests-performance
Command: npx skills add https://github.com/greglas75/zuvo --skill tests-performance-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Slow test suites waste developer time and delay feedback loops, but teams often lack a systematic way to measure baseline performance, audit runner configuration, and identify which fixes deliver the most speedup. ## Core Features & Use Cases - Baseline Measurement: Runs the test suite multiple times, computes median timing and stability, and saves a baseline JSON for later comparison. - TP1-TP17 Config Audit: Scores Vitest, Jest, or pytest configuration against a 17-item checklist covering transforms, workers, caching, coverage tools, and isolation. - Slow Test Classification: Identifies the slowest test files and classifies causes such as heavy setup, real timers, DOM-heavy rendering, and sequential async calls. - Use Case: A team with a 10-minute Jest suite runs a full audit, discovers the transform is not using @swc/jest and workers are misconfigured, applies the ranked config diffs, then verifies a 40% speedup against the saved baseline. ## Quick Start Run a full test suite performance audit on this project and produce an impact-ranked action plan.

Frequently Asked Questions about tests-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I speed up a slow Jest or Vitest test suite?

Start by measuring a baseline with multiple runs, then audit the runner configuration against a checklist covering transforms, worker strategy, caching, and environment settings. Config changes like switching to @swc/jest or enabling thread pools often outperform rewriting individual tests.

How to find the slowest tests in my test suite?

Run the suite with JSON reporting (vitest --reporter=json, jest --json, or pytest --durations=0) to get per-file timing. Then classify the slowest files by cause: heavy setup, real timers, DOM-heavy rendering, large fixtures, or sequential async calls.

Does this test performance audit support pytest?

Yes, pytest is supported alongside Vitest and Jest. Detection looks for pytest.ini, setup.cfg, or [tool.pytest] in pyproject.toml, and timing uses pytest --durations=0. Some checklist items like transform efficiency are marked N/A for pytest.

Can I audit test configuration without running the test suite?

Yes, the --no-run mode skips test execution and audits only the runner configuration plus a static pattern scan for slow-test anti-patterns. The action plan is reported without measured impact, and no baseline is created.

Does the audit modify my test configuration automatically?

No, the audit only measures, scores, and proposes exact config diffs. Applying changes is the user's decision, and the verify mode re-measures after changes are applied to confirm actual speedup against the saved baseline.