warp-integration-test

Automate creation, execution, and debugging of Warp integration tests.

Updated Apr 28, 2026

Search Tags:#rust #integration-testing #builder #nextest #test-automation #warp

Ready to run

npx skills add https://github.com/89jobrien/warpx --skill warp-integration-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: warp-integration-test
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/warp-integration-test
Command: npx skills add https://github.com/89jobrien/warpx --skill warp-integration-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes, runs, and debugs Warp integration tests using a custom Builder/TestStep framework, enabling hermetic and reproducible test execution for end-to-end UI and terminal behaviors.

Core Features & Use Cases

Supports Rust integration tests within Warp's custom framework under crates/integration.
Provides a manual runner and Nextest-compatible workflow to exercise end-to-end UI and terminal behaviors.
Guides test authors from scaffolding to execution, ensuring hermetic home directories, isolated envs, and artifact export.

Quick Start

Run a named Warp integration test using the integration runner.

Frequently Asked Questions about warp-integration-test

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

FAQPage Schema

How do I automate end-to-end UI and terminal verification for Rust integration tests?▼

Automating Rust integration tests for UI and terminal verification involves using a custom Builder and TestStep framework. This structures test driver setup and execution to validate complex terminal behaviors hermetically.

What is the best way to run Warp integration tests using Nextest?▼

Running Warp integration tests using Nextest is supported via a compatible workflow alongside a manual runner. This allows you to exercise end-to-end UI and terminal behaviors while maintaining reproducible test execution environments.

How do I ensure hermetic test environments and isolated home directories in Rust integration tests?▼

Ensuring hermetic test environments and isolated home directories requires a structured workflow that guides test authors from scaffolding to execution. This setup isolates environments and handles artifact export via an on_finish abstraction.

Does the Warp integration testing framework support manual runners alongside Nextest?▼

Yes, the Warp integration testing framework supports both a manual runner and a Nextest-compatible workflow. This allows developers to exercise end-to-end UI and terminal behaviors through their preferred test automation tool.

How do I handle test artifacts and outputs when debugging Warp integration tests?▼

Handling test artifacts when debugging Warp integration tests is managed through an on_finish abstraction. This mechanism provides structured artifact handling after test execution, ensuring outputs are exported and available for validation.

What are the limitations of using a Builder and TestStep abstraction for test automation?▼

The Builder and TestStep abstractions are tailored specifically for Rust integration tests within Warp's custom framework under crates/integration. This specialized design means they may not generalize to other test automation frameworks or non-Rust environments.