dev_test_suite

Run cargo test across backend, core, and frontend crates to detect regressions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maisonnat/axur-tool --skill dev-test-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev_test_suite
Source: https://github.com/maisonnat/axur-tool/tree/main/.agent/skills/dev_test_suite
Command: npx skills add https://github.com/maisonnat/axur-tool --skill dev-test-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams verify code changes by running unit and integration tests to detect regressions and logic errors before merging.

Core Features & Use Cases

  • Comprehensive testing: Executes the workspace tests across all crates to ensure baseline functionality.
  • Targeted testing: Allows running tests for specific crates (axur-backend, axur-core, axur-frontend) as needed.
  • Quality gate: Serves as part of the VERIFY phase in local development to prevent faulty code from advancing.

Quick Start

Run all workspace tests to confirm that changes have not introduced regressions.

Frequently Asked Questions about dev_test_suite

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

FAQPage Schema
How do I run automated tests to catch regressions in a Rust workspace?

To run automated tests and catch regressions, execute workspace tests across all crates to verify baseline functionality. This integrates directly with cargo test to detect logic errors before merging.

Can I run cargo test for a specific crate instead of the whole workspace?

Yes, you can run targeted testing for specific crates like axur-backend, axur-core, or axur-frontend. This isolates and verifies changes within individual crates rather than executing the entire workspace test suite.

What is the best way to inspect test failures and handle common errors in Rust?

Inspect cargo test output to diagnose logic errors and regressions. This process provides guidance for output inspection and common failure handling to identify faulty code before it advances.

Does this testing workflow support integration tests and unit tests simultaneously?

Yes, the workflow supports unit tests and integration tests simultaneously. It identifies and runs the project's tests to detect regressions and logic errors across backend, core, and frontend crates.

When do I need to run workspace tests during the development lifecycle?

Run workspace tests during the VERIFY phase of local development before commits, merges, or releases. This acts as a quality gate to prevent faulty code from advancing into the main branch.