test

Name: test
Availability: InStock
Author: bernajaber

Run and validate automated acceptance tests for product features.

Updated Feb 26, 2026

Search Tags:#testing #spec-driven #nodejs #test-automation #assert #regression-testing #acceptance-tests

Ready to run

npx skills add https://github.com/bernajaber/pi-product-system --skill test-bernajaber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/test
Command: npx skills add https://github.com/bernajaber/pi-product-system --skill test-bernajaber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures every acceptance scenario described in the specification is implemented, executed, and passing so that new features do not introduce regressions or incomplete behavior.

Core Features & Use Cases

Spec-driven testing: Reads .pi/specs/<feature>/spec.md and .pi/specs/<feature>/plan.md to derive test cases for each acceptance scenario.
Cross-runtime support: Guides test creation for Node.js, Python, Go, shell, and static web apps with clear rules (one file per feature, deterministic assertions).
Regression protection: Runs all existing feature tests and requires fixes for any regressions before marking progress and committing passing tests.

Quick Start

Run the test skill to generate, execute, and commit deterministic acceptance tests for the current feature based on .pi/specs/<feature>/spec.md.

Frequently Asked Questions about test

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

FAQPage Schema

How do I automate acceptance tests for spec-driven development?▼

To automate acceptance tests for spec-driven development, you can use a skill that reads .pi/specs directories to derive and execute test cases. It validates each acceptance scenario against your codebase using built-in assertions to ensure features pass reliably.

Can I run regression tests across Node.js, Python, and Go projects?▼

Yes, you can run regression tests across Node.js, Python, Go, and shell projects. The testing process requires deterministic, fast, single-file-per-feature test implementations using built-in assertions to validate behavior across these runtime environments.

What is the best way to ensure acceptance scenarios pass reliably in continuous integration?▼

The best way to ensure acceptance scenarios pass reliably is to execute spec-driven tests that return non-zero exit codes on failures. This approach catches incomplete behavior and regressions by validating committed codebases against defined specifications before progressing.

Do I need a specific directory structure for automated acceptance testing?▼

Yes, automated acceptance testing requires a committed codebase with .pi/specs and tests directories. You need spec.md and plan.md files within .pi/specs/<feature>/ to derive the test cases and guide the single-file-per-feature test implementations.

Why do my regression tests fail when verifying new features?▼

Regression tests fail during new feature verification when existing acceptance scenarios are broken. The testing process detects these regressions, requires fixes before marking progress, and enforces committing only passing tests to prevent incomplete behavior in the repository.