smoke-test

Automate end-to-end smoke testing for the wasteland wl binary.

86|30|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gastownhall/wasteland --skill smoke-test-gastownhall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/gastownhall/wasteland/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/gastownhall/wasteland --skill smoke-test-gastownhall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a freshly built wl binary passes the predefined smoke test plan to catch regressions early and prevent faulty deployments.

Core Features & Use Cases

  • Automates the end-to-end smoke testing workflow for the wasteland wl binary.
  • Ensures build integrity, environment isolation, and deterministic test results.
  • Use Case: A developer validates that a new wl binary passes all smoke tests before pushing changes.

Quick Start

Run the smoke tests defined in test/smoke/TESTPLAN.md from the repo root.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate smoke tests for a newly built binary to catch regressions before deployment?

Automate smoke tests for a built binary by running predefined end-to-end checks to verify build integrity and runtime behavior, catching regressions early and preventing faulty deployments before pushing changes.

What is a deterministic smoke test plan and how does it verify build integrity?

A deterministic smoke test plan drives consistent end-to-end checks from a local TESTPLAN.md file to verify build integrity, ensuring environment isolation and reliable test results for a freshly built binary.

How do I run smoke tests from the repository root using a Makefile-based build?

Run smoke tests from the repository root by executing the Makefile-based build process, which isolates the environment and applies the local test plan to verify the binary's runtime behavior.

Do I need a specific test plan file to execute automated smoke tests?

Yes, automated smoke testing requires a local test plan located at test/smoke/TESTPLAN.md to drive deterministic checks and validate the freshly built binary's runtime behavior.

Can I use this smoke testing workflow to validate environment isolation and runtime behavior?

Yes, the smoke testing workflow validates environment isolation and runtime behavior by applying deterministic end-to-end checks from the test plan to ensure the built binary operates correctly.

Why does my binary need end-to-end smoke testing before pushing code changes?

End-to-end smoke testing is needed before pushing changes to ensure the freshly built binary passes the predefined test plan, verifying build integrity and preventing regressions from reaching deployment.