warp-integration-test

Warp integration tests use a custom Builder/TestStep framework under crates/integration to orchestrate end-to-end test execution. This setup drives a real app instance with synthetic UI and terminal events for deterministic validation.

A hermetic testing framework isolates test environments by booting a real app instance with a dedicated HOME directory, isolated rc files, and file-backed user preferences. This ensures deterministic end-to-end validation without external interference.

Collect screenshots, logs, and test results by utilizing artifacts and on_finish hooks within the test framework. These components automatically gather debugging outputs after the synthetic UI and terminal events complete execution.

Yes, the Warp integration test driver supports automatic reruns specifically when precondition failures occur. This prevents transient environment setup issues from causing false-negative test failures during end-to-end validation.

Yes, the framework supports configurable real-display options for end-to-end verification. This allows developers to visually inspect synthetic UI and terminal events on an actual display during test execution.

The framework integrates with test drivers like nextest to run named Warp integration tests and exercise end-to-end flows. It leverages these tools to manage the execution of the custom Builder/TestStep framework.