unit-test-runner

Execute unit test suites across 7 programming languages with 2026 runner configurations.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill unit-test-runner-robotijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unit-test-runner
Source: https://github.com/robotijn/ctoc/tree/main/skills/testing/runners/unit-test-runner
Command: npx skills add https://github.com/robotijn/ctoc --skill unit-test-runner-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually running unit test suites leads to missed coverage gaps, undetected flaky tests, and misconfigured runners that waste CI compute or produce unreliable results. This skill automates test execution with 2026 industry best practices to ensure fast, reproducible, reliable test runs as the mandatory Step 14 VERIFY quality gate before code ships.

Core Features & Use Cases

  • Multi-language test execution: Runs unit test suites for TypeScript/JavaScript, Python, Go, Rust, C#, Java, C/C++, and SQL using 2026 best-practice runner configurations (parallel execution, seeded random ordering, process isolation, fail-fast for PRs, CI sharding).
  • Comprehensive result reporting: Delivers full test result summaries (pass/fail/skipped/cached counts), coverage metrics (line, branch, new code), performance timings (slowest tests, per-shard wall-clock), flake signals, and cache hit rates.
  • Quality gate enforcement: Blocks phase advancement for critical misconfigurations (serial execution on multi-core, no worker isolation, unseeded random ordering, skipped tests, flaky tests) and emits structured findings for the refinement loop.
  • Use Case: For a SaaS team with a 30-second test suite, this skill ensures tests run in under 10 seconds in CI, catches flaky tests before they reach production, and enforces 80% coverage on all new code as a non-negotiable deployment gate.

Quick Start

Use the unit-test-runner skill to execute your project's unit test suite, receive a full report of test results, coverage metrics, performance timings, and any critical test execution misconfigurations that block the quality gate.

Frequently Asked Questions about unit-test-runner

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

FAQPage Schema
How do I enforce coverage thresholds and fail-fast execution for unit tests in CI?

Unit test suites are executed using 2026 best-practice runner configurations that enforce parallel execution, seeded random ordering, process isolation, and fail-fast for pull requests to produce reliable results.

How does flaky test detection work in a CI testing pipeline?

Flaky test detection in a CI testing pipeline works by executing unit tests with seeded random ordering and process isolation, then reporting flake signals to block quality gate phase advancement before code ships.

Can I run test sharding for large test suites across multiple programming languages?

Yes, you can run test sharding for large test suites across TypeScript, Python, Go, Rust, C#, Java, C/C++, and SQL, reporting per-shard wall-clock performance timings to optimize CI compute.

What is a quality gate misconfiguration in unit testing?

A quality gate misconfiguration in unit testing is a critical runner setup flaw like serial execution on multi-core, no worker isolation, unseeded random ordering, or skipped tests, which blocks phase advancement to ensure reliable results.

How do I report line, branch, and new code coverage metrics for a quality gate?

You report line, branch, and new code coverage metrics for a quality gate by executing unit test suites with best-practice runner configurations that deliver comprehensive test result summaries and enforce coverage thresholds.