zoo-test-writing

Write and validate focused integration tests for Zoo subtasks.

5|1|Updated Aug 22, 2025

Search Tags:#testing #qa #subtasks #integration-tests #test-writing #zoo #failure-first

Ready to run

npx skills add https://github.com/andreyvit/zoo --skill zoo-test-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zoo-test-writing
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-test-writing
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-test-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write or update tests that define the expected behavior for a Zoo active subtask, ensuring testing is performed only when explicitly requested.

Core Features & Use Cases

Prefer failing-first tests and verify the failure reason matches intent.
Keep test scope focused on the active (next) subtask.
Use integration tests by default unless algorithmic code justifies unit tests.
For wiring components, use integration tests with real production objects and maintain testability hooks.

Quick Start

Write a focused test for the next active subtask and run the test suite to verify the failure reason before adding another.

Frequently Asked Questions about zoo-test-writing

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

FAQPage Schema

How do I write integration tests for active subtasks?▼

Integration tests for active subtasks are written by focusing test scope on the next subtask, using real production objects for wiring components, and verifying the failure reason matches intent before adding another test. This ensures correctness across planning and execution phases.

What is the failure-first approach in test writing?▼

The failure-first approach in test writing involves creating a focused test for the next active subtask and running the suite to verify the failure reason matches your intent. This validates expected behavior before implementation proceeds.

When should I use unit tests instead of integration tests?▼

Unit tests should only be used instead of integration tests when dealing with algorithmic code. Integration tests are the default for Zoo subtasks to maintain testability hooks and validate wiring with real production objects.

How do I keep test scope focused on a single subtask?▼

To keep test scope focused on a single subtask, write targeted tests that define expected behavior only for the next active subtask. Enforce minimal test boilerplate and clear failure signals to ensure correctness during planning and review.

Does Zoo test writing require testability hooks for component wiring?▼

Yes, testability hooks are required for component wiring. Integration tests use real production objects alongside these hooks to validate the expected behavior of the next active subtask across review and execution phases.