testing

Coordinate multi-tier testing with deterministic CLI commands across development cycles.

Updated Feb 24, 2021
One-click install
npx skills add https://github.com/roderik/roderik.github.io --skill testing-roderik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/roderik/roderik.github.io/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/roderik/roderik.github.io --skill testing-roderik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for multi-tier testing to ensure rapid, reliable feedback across development stages.

Core Features & Use Cases

  • Four-tier testing: Fast, Checkpoint, Full, and Manual, each progressively broader and automated or manual as needed.
  • CI governance and guardrails: Enforces a zero-tolerance policy and cross-package consistency to prevent regressions.
  • Flow integrations: Works with related skills like evidence, execute, verifier, planner, sweep, and tdd to coordinate testing workflows across the project.

Quick Start

Run the fast CI after edits to receive immediate feedback on changes.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I structure multi-tier testing for fast CI feedback during active development?

Multi-tier testing structures checks into Fast, Checkpoint, Full, and Manual tiers to provide rapid, consistent feedback across development cycles. It sequences fast checks and unit tests before broader integration tests to validate code quality efficiently.

What is the best way to enforce quality gates in a pre-PR CI pipeline?

Enforcing quality gates in a pre-PR pipeline requires a zero-tolerance policy and cross-package consistency to prevent regressions. Running deterministic checkpoint commands validates code quality before phase transitions or pull requests.

How does multi-tier testing integrate with TDD and planner workflows?

Multi-tier testing integrates with TDD, planner, evidence, and verifier skills to coordinate testing workflows across the project. These flow integrations sequence automated checks and manual verification with evidence flows to validate code.

Can I run automated unit tests and integration tests sequentially across development cycles?

Yes, you can run automated unit tests and integration tests sequentially across development cycles. The framework coordinates fast checks first, then progressively broader integration tests, using deterministic CLI commands to ensure consistent feedback.

Why does cross-package consistency matter in CI guardrails for automated testing?

Cross-package consistency matters in CI guardrails because it enforces a zero-tolerance policy against regressions across all project packages. This ensures deterministic CLI commands return predictable results and maintain code quality throughout phase transitions.