gui-integration-test — Claude Code skill: Warp GUI integration tests
gui-integration-test is a Claude Code skill that writes and debugs integration tests for Warp's GUI desktop app on the Builder/TestStep harness. Runs when a test is added or fixed.
AGPL-3.0 ★ 720 updated 2026-11-10
npx skills add dominikmartn/harp --skill gui-integration-test -a claude-codeWhat gui-integration-test does
Each test boots a real Warp instance with a throwaway home directory, feeds it synthetic UI and terminal events, then polls assertions until they pass or time out. Scope is the GUI desktop front-end (app/ crate on WarpUI); headless TUI work belongs to the separate TUI skills.
A test starts as pub fn name() -> Builder in a module under crates/integration/src/test/, gets exported from test.rs, and is registered with register_test! in crates/integration/src/bin/integration.rs. The outer harness in crates/integration/tests/common/mod.rs shells out to that binary and retries the run up to 10 times when it exits with the rerun code.
Being present under src/test/ does not make a test run: it also has to be listed in ui_tests.rs or shell_integration_tests.rs, otherwise cargo nextest never picks it up. The harness swaps HOME for a temp directory and writes minimal rc files, so real dotfiles and saved Warp settings stay out of the run.
What it helps with
- scaffold a new integration test under
crates/integration/src/test/ - trace a failing test that exits with the rerun code
- wire a test into nextest and the manual runner
- check shell integration across bash, zsh and fish
- move deterministic logic out of a slow app-boot test into a unit test
Example prompts for the agent
- Add an integration test for moving focus between panes and register it in
ui_tests.rs. - The test in
shell_integration_tests.rskeeps exiting with the rerun code, find out why and fix it. - Check that the new test shows up in both
cargo nextestand the manual runner.
How to install gui-integration-test
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill gui-integration-test -a claude-code2Manually: put the files in place
~/.claude/skills/gui-integration-test/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gui-integration-test/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill gui-integration-test -a codex2Manually: put the files in place
.agents/skills/gui-integration-test/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill gui-integration-test -a cursor2Manually: put the files in place
.cursor/skills/gui-integration-test/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dominikmartn/harp .agents/skills/gui-integration-test2Manually: put the files in place
.github/skills/gui-integration-test/SKILL.md1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill gui-integration-test -a gemini-cli2Platform CLI
gemini skills install https://github.com/dominikmartn/harp --path .agents/skills/gui-integration-testManually: put the files in place
.devin/skills/gui-integration-test/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gui-integration-test
How do I install gui-integration-test in Claude Code?
Run npx skills add dominikmartn/harp --skill gui-integration-test -a claude-code. The skill file lands at ~/.claude/skills/gui-integration-test/SKILL.md.
What does gui-integration-test do?
It covers writing and debugging integration tests for Warp's GUI desktop app: where the test function lives, how to register it, and how it reaches the manual runner and nextest.
Does the skill work for the TUI?
No, it targets the GUI desktop front-end (app/ on WarpUI). Headless TUI code in crates/warp_tui has its own skills: tui-ui-guidelines, tui-testing and tui-verify-change.