warp-integration-test

To run integration tests for Warp terminal UI and behavior, execute the command `cargo run -p integration --bin integration -- test_name`. This boots a real Warp app instance with an isolated test environment and drives it using synthetic UI and terminal events.

Assertion polling in Warp terminal testing works by continuously checking expected outcomes until success or a specified timeout occurs. This mechanism ensures that synthetic UI and terminal events have fully propagated through the real app instance before validating the test result.

Yes, you need Rust to execute Warp integration tests. The custom integration framework is built within the `crates/integration` directory and requires the Cargo build system to compile the test suite and boot the real Warp app instance.

The best way to simulate user interactions in a Warp terminal test is by using the custom Builder/TestStep framework. This framework drives the real Warp app instance with synthetic UI and terminal events, allowing you to assert end-to-end behavior within an isolated environment.

Yes, you can debug end-to-end UI behavior in Warp using a custom Builder/TestStep framework. This framework boots a real Warp app instance in an isolated test environment, drives it with synthetic events, and polls assertions until success or timeout to pinpoint failures.

A custom integration framework is used instead of standard Rust test crates for Warp because it provides specialized features like booting real app instances, driving synthetic UI and terminal events, and polling assertions until success or timeout to handle asynchronous terminal behavior.