t-backend-test-run

Automate targeted Rust backend test execution and failure diagnosis.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-backend-test-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-backend-test-run
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-backend-test-run
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-backend-test-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates focused Rust backend testing to quickly identify failures, translate them into actionable fixes, and preserve the intended behavior of scenario tests during revalidation.

Core Features & Use Cases

  • Targeted test execution and failure diagnosis for backend tests.
  • Automated delegation of production code repairs to resolve failures without altering test semantics.
  • Controlled re-test workflow that emphasizes strict adherence to scenario test semantics and flow continuity.
  • Supports deterministic runner items and coordination with backend Dev subagents.

Quick Start

Run the t-backend-test-run workflow on a failing backend feature to diagnose issues, delegate fixes, and re-run tests while preserving scenario semantics.

Frequently Asked Questions about t-backend-test-run

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

FAQPage Schema
How do I automate Rust backend test failure diagnosis and re-runs?

Automate Rust backend test failure diagnosis by targeting specific failing tests, classifying the failures, and delegating production code repairs before re-running. The workflow preserves scenario test semantics and coordinates fixes through backend Dev subagents.

Can I fix backend test failures without altering the original test scenarios?

Yes, you can fix backend test failures without altering test scenarios. The workflow delegates production code repairs to resolve failures while strictly preserving the intended behavior and integrity of scenario tests during revalidation.

What is the best way to orchestrate Rust backend test selection and failure recovery?

Orchestrate Rust backend test selection and failure recovery through a safe, auditable workflow with clear prompts for agents. It coordinates deterministic runner items, failure classification, and check and acceptance gates before completion.

Does automated backend testing support coordination with backend Dev subagents?

Yes, automated backend testing supports coordination with backend Dev subagents. It delegates production code repairs to these subagents to resolve identified failures while maintaining strict adherence to scenario test flow continuity.

Why do I need acceptance gates before completing an automated backend test re-run?

Acceptance gates are required before completing an automated backend test re-run to enforce a safe, auditable workflow. They ensure failure fixes strictly adhere to scenario test semantics and verify resolution before final completion.

When should I not use automated test delegation for Rust backend failures?

Avoid using automated test delegation when deterministic runner items are unavailable or when fixes require altering scenario test semantics. The workflow strictly preserves test integrity and orchestrates only production code repairs.