swain-test

Run two-phase integration and smoke tests via swain-test.sh outputs.

2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/cristoslc/swain --skill swain-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swain-test
Source: https://github.com/cristoslc/swain/tree/main/skills/swain-test
Command: npx skills add https://github.com/cristoslc/swain --skill swain-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Two-phase gate that runs deterministic integration tests followed by agent-driven smoke tests to verify behavior against acceptance criteria and project declarations.

Core Features & Use Cases

  • Phase 1 runs deterministic integration tests via swain-test.sh.
  • Phase 2 runs agent-driven smoke tests that verify observable behavior against spec acceptance criteria, changed skills, and declared smoke items.
  • Ties into swain-sync before commits and swain-release before cutting a release, emitting structured evidence sections.

Quick Start

Run the gate to execute integration tests and smoke checks before committing or releasing.

Frequently Asked Questions about swain-test

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

FAQPage Schema
How do I automate integration tests and smoke checks before a release?

Automate integration tests and smoke checks by running a two-phase gate that executes deterministic integration tests followed by agent-driven smoke verification. This validates behavior against acceptance criteria before committing or cutting a release.

What is a two-phase testing gate for CI workflows?

A two-phase testing gate runs deterministic integration tests first, then executes agent-driven smoke tests to verify observable behavior. It structures evidence for downstream traceability and ensures decisions are honored before commits or releases.

How do I run integration tests using swain-test.sh outputs?

Run integration tests by sourcing dependency results from swain-test.sh outputs including INTEGRATION, ARTIFACTS, SKILLS, and SMOKE. The gate uses these structured outputs to validate work and apply governance to release workflows.

Does the swain-test gate work with swain-sync and swain-release workflows?

The swain-test gate ties directly into swain-sync before commits and swain-release before cutting a release. It emits structured evidence sections to ensure governance decisions are honored downstream in the workflow.

Can I use agent-driven smoke tests to verify spec acceptance criteria?

Yes, phase 2 of the gate runs agent-driven smoke tests that verify observable behavior against spec acceptance criteria, changed skills, and declared smoke items. This ensures the software meets the defined requirements.

What are the limitations of running integration and smoke tests in a single gate?

The gate requires swain for governance and release workflows, and sources dependency results from swain-test.sh outputs. Projects not using the swain framework cannot utilize this two-phase testing gate for traceability.