executing-backend-unit-tests

Execute backend unit tests in a sandbox and emit a coverage-gated PASS, FAIL, or ERROR verdict.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill executing-backend-unit-tests-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-backend-unit-tests
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/executing-backend-unit-tests
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill executing-backend-unit-tests-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running backend unit tests before a merge often produces unreliable results: self-declared coverage numbers, flaky tests passed by luck, and verdicts with no runner evidence. This Skill executes the backend unit suite through the CI/test runner in a sandbox, measures real line coverage, surfaces flaky tests, and emits an auditable gate verdict that feeds a human verification layer. ## Core Features & Use Cases - Runner-backed execution: Runs Go and equivalent backend unit tests via the CI/test runner in a sandbox, capturing per-test results with reproduction commands. - Measured coverage gate: Reads line coverage from the runner report and applies a configurable threshold (default 0.80); unmeasurable coverage is treated as a failure. - Flaky test detection: Re-runs suspect tests a bounded number of times and marks non-deterministic results instead of passing them. - Use Case: Before merging a backend change in a banking CI pipeline, run the unit suite against the built artifacts and receive a PASS/FAIL/ERROR verdict with totals, coverage, failure details, and an audit ID for human sign-off. ## Quick Start Run the backend unit tests against the built artifacts in the sandbox and give me the pass/fail gate with measured coverage.

Frequently Asked Questions about executing-backend-unit-tests

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

FAQPage Schema
How do I run backend unit tests in CI with a coverage gate?▼

Provide the built backend artifacts, a reachable sandbox target environment, and an idempotency key. The suite runs through the CI/test runner, and a PASS verdict requires zero failed tests plus measured line coverage at or above the threshold, which defaults to 0.80.

How is code coverage measured for the pass/fail gate?▼

Coverage is read directly from the runner report, such as a Go coverage profile, never from a self-declared number. If coverage cannot be measured, it is reported as null and treated as below threshold, so the gate cannot pass.

Can this skill fix failing backend tests automatically?▼

No. It only executes tests and reports results; it never writes, edits, or fixes tests or production code. Failures are routed to a separate fixer such as progressive-bug-hunter, and the verdict feeds a human verification layer.

What happens when backend tests are flaky or non-deterministic?▼

Suspect tests are re-run a bounded number of times. If results differ across runs, the test is marked flaky and excluded from a PASS, then reported in the failures list for stabilization rather than being passed by luck.

When should I not use backend unit test execution?▼

Do not use it to design the test plan, run frontend unit, integration, or e2e suites, or write code. Those belong to dedicated skills such as planning-banking-tests, executing-frontend-unit-tests, executing-integration-tests, and authoring-e2e-test-suite.