Test Writing Skill

Write and execute deterministic Simple BDD tests with strict failure discipline.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ormastes/Spipe --skill test-writing-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Test Writing Skill
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/test
Command: npx skills add https://github.com/ormastes/Spipe --skill test-writing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you write clear, deterministic test specifications and run them confidently without silently ignoring failures.

Core Features & Use Cases

  • Test writing rules & discipline: Enforces that failing tests must not be skipped without explicit approval, so regressions are caught early.
  • Practical test execution guidance: Covers selecting tests (single file, list, slow-only, tag filtering) and running in isolated containers.
  • Consistent BDD test structure: Provides conventions for BDD syntax, documentation style (docstring markdown), and using matchers correctly for readable assertions.
  • Run tracking & UI system testing: Documents how to track test history and how to test Web UI/TUI via an HTTP test API client.

Quick Start

Ask the skill to help you write a BDD test file named *_spec.spl using docstring markdown and built-in matchers, then run all tests to confirm your changes are safe.

Frequently Asked Questions about Test Writing Skill

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

FAQPage Schema
How do I write BDD tests that prevent silent failures?

BDD tests that prevent silent failures require strict discipline against skipping failing cases without explicit approval. The Test Writing Skill enforces deterministic test specifications, ensuring regressions are caught early and never silently ignored.

What is the correct syntax for Simple BDD test files?

Simple BDD test files must follow a prescribed syntax using docstring markdown for documentation and built-in matchers for readable assertions. Files should be named using the *_spec.spl convention to maintain consistent BDD test structure.

How do I run container-isolated tests and filter by tags?

Container-isolated tests support execution with test selection options including single file, list, slow-only, and tag filtering. Running tests in isolated containers ensures deterministic execution while selecting specific tagged tests validates targeted changes.

Can I test Web UI and TUI systems using an HTTP test API?

Web UI and TUI systems can be tested via an HTTP test API client. The Skill documents how to interact with this API client to perform UI system testing and validate user interface behavior deterministically.

Does this approach support tracking test run history?

Test run history tracking is supported through proper run tracking integration. The Skill documents how to configure run tracking to maintain a record of test executions and monitor test history over time.

What are the limitations of using built-in matchers for test assertions?

Built-in matchers are the only allowed assertion mechanism, restricting you to the provided set of matchers for readable BDD tests. System tests optionally support cover annotations, but you cannot use external or custom matcher libraries.