test-runner

Identify test failures with source locations across Vitest or Jest.

Updated Aug 23, 2026

Search Tags:#testing #failures #rerun #structured-results #source-maps

Ready to run

npx skills add https://github.com/Technikhighknee/agent-workbench --skill test-runner-technikhighknee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/Technikhighknee/agent-workbench/tree/main/.claude/skills/test-runner
Command: npx skills add https://github.com/Technikhighknee/agent-workbench --skill test-runner-technikhighknee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests should clearly report failures with location and context. This Skill returns structured test results and failures.

Core Features & Use Cases

Structured results: Pass/fail with locations and maps.
Failure details: Exact source locations and expected vs actual.
Use Case: Quickly rerun only failing tests after a change.

Quick Start

run_tests({})

Frequently Asked Questions about test-runner

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

FAQPage Schema

How do I identify exactly what test failed and where in my JavaScript or TypeScript project?▼

Test runners like Jest and Vitest report pass/fail results with source maps that pinpoint exact file paths and line numbers where failures occurred, showing precisely what assertion failed and why.

Can I rerun only the tests that failed after making code changes?▼

Yes. Structured test results identify which specific tests failed, allowing you to target and rerun only those failing tests rather than running your entire test suite each time.

How do I get detailed failure information including expected vs actual values?▼

Structured test result reporting provides complete failure details—expected versus actual values, stack traces with source maps, and exact locations—enabling fast diagnosis of what went wrong.

Does this work with both Jest and Vitest?▼

Yes. This integrates with both Jest and Vitest, the two primary test frameworks for JavaScript and TypeScript projects, supporting structured failure reporting across either framework.

What's the fastest way to debug test failures after code changes?▼

Use structured test results with source maps to instantly locate failures by file and line number, then rerun only those specific failing tests to validate fixes without full test suite overhead.