tester

Plan behavior-based tests with edge-case selection and regression checks.

20|4|Updated May 14, 2026
One-click install
npx skills add https://github.com/crewrig/crewrig --skill tester-crewrig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tester
Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/tester
Command: npx skills add https://github.com/crewrig/crewrig --skill tester-crewrig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design tests that catch real regressions without wasting time on low-value coverage, so changes stay reliable and maintainable.

Core Features & Use Cases

  • Test strategy planning: Choose the smallest observable behavior to validate instead of testing implementation details.
  • Edge-case selection: Prioritize golden-path, boundary, known-bad, concurrency, and partial-failure cases in the right order.
  • Regression verification: Turn bug fixes into durable tests that fail for the right reason and prove the fix actually works.
  • Example use case: A feature is added, and you need a concise test plan that covers the important success path plus the few failure cases that matter.

Quick Start

Ask for a focused test plan for the feature or bug fix, including the smallest behavior to test, the key edge cases, and the exact regression checks to add.

Frequently Asked Questions about tester

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

FAQPage Schema
How do I write a test plan that validates behavior instead of implementation details?

A high-signal test strategy selects the smallest observable behavior to validate, avoiding implementation details. It prioritizes golden-path, boundary, known-bad, and concurrency cases to catch real regressions while maintaining reliable and maintainable test coverage.

What is the best way to turn a bug fix into a durable regression test?

To turn a bug fix into a regression test, write a test that fails for the exact known-bad reason before the fix is applied, then passes afterward. This empirical verification proves the fix works and prevents future regressions across application code and integration surfaces.

How do I select edge cases for test coverage without wasting time on low-value tests?

Edge-case selection prioritizes golden-path, boundary, known-bad, concurrency, and partial-failure cases in a specific order. This disciplined test selection ensures coverage focuses on high-value scenarios that validate behavior and catch real regressions efficiently.

Can I use this test strategy for both feature work and integration surfaces?

Yes, this test strategy applies to feature work, bug fixes, test reviews, and edge-case analysis across application code and integration surfaces. It requires disciplined test selection, behavior-based naming, arrange-act-assert structure, and empirical verification of tool availability.

What are the limitations of behavior-based testing for complex concurrency scenarios?

Behavior-based testing handles concurrency and partial-failure cases through disciplined edge-case selection. However, it requires empirical verification of tool availability and focuses on the smallest observable behavior, which may limit coverage of deeply nested integration surface interactions.