test-smoke-integration

Name: test-smoke-integration
Availability: InStock
Author: victorp1leon

Execute smoke and integration tests and store summary artifacts and history logs.

Updated Mar 6, 2026

Search Tags:#debugging #reports #validation #end-to-end #integration-testing #smoke-testing

Ready to run

npx skills add https://github.com/victorp1leon/openclaw-bakery --skill test-smoke-integration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-smoke-integration
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/test-smoke-integration
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill test-smoke-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates end-to-end OpenClaw behavior by executing smoke and integration validations, summarizing results, and exposing artifacts for quick diagnosis.

Core Features & Use Cases

Default mock-safe smoke and integration validation to verify baseline behavior.
Optional live validations when explicitly requested, with appropriate environment checks.
Access to summary artifacts in reports for quick review and traceability.
Guided failure diagnosis via latest summary and per-run history logs.

Quick Start

Run the default smoke-integration summary workflow to validate end-to-end behavior.

Frequently Asked Questions about test-smoke-integration

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

FAQPage Schema

What is end-to-end smoke and integration testing for operational flows?▼

End-to-end smoke and integration testing validates baseline behavior by executing mock and live validation scenarios, surfacing standardized summary artifacts to quickly diagnose operational flow failures.

How do I run a default smoke and integration validation?▼

To run a default smoke-integration validation, execute the standard workflow to verify end-to-end behavior using mock-safe scenarios, which generates summary artifacts and history logs for traceability.

Can I execute live integration validations against my environment?▼

Yes, you can execute live integration validations when explicitly requested, allowing the process to perform appropriate environment checks before running end-to-end tests against live systems.

How do I diagnose failures from integration test runs?▼

Diagnose integration test failures by reviewing the latest summary artifacts and per-run history logs, which provide verbose traceability and detailed reports for guided failure analysis.

What is the best way to coordinate mock and live validation scenarios?▼

The best way to coordinate mock and live validation scenarios is using a workflow that defaults to mock-safe testing, switching to live validations only when explicitly requested with environment checks.