Testing

gpty’s test strategy combines automated CI checks with a manual pre-release smoke test suite. Automated tests cover all pure-logic paths in Rust and GDScript; manual tests cover GUI interaction, IPC bridge roundtrips, and daemon lifecycle that require a running Godot instance.

Automated (CI)

Run on every push and pull request:

# Rust — unit tests, integration tests, doctests
cargo test --workspace
cargo clippy -- -D warnings
cargo fmt --check

# GDScript — unit + integration tests
godot --headless --path godot --import
godot --headless --path godot -s addons/gut/gut_cmdln.gd -d \
  -gdir=res://tests/unit -gdir=res://tests/integration

Rust coverage: core engine (parser, keymap, grid, concept routing, capture state machine, history), IPC types + protocol, CLI schema generation, GDExtension FFI functions. Tile layout algorithms are integration-tested in crates/gpty-core/tests/tile_layout.rs, which mirrors the GDScript split/kill/expand logic in godot/scenes/terminal/terminal_manager.gd — algorithm changes must be mirrored in both files.

GDScript coverage: concept merge/save/load, terminal manager tile lifecycle (spawn, kill, swap, labels, grid-full refusal), settings save/load roundtrip, profile CRUD, layout save/restore, sidebar signal emission, pane settings application, IPC routing logic (error format, listPanes, killPane, layoutList), palette command generation.

Known gaps (not automatable in headless CI):

• Workspace class cannot be instantiated in headless GUT (depends on GptyTerminal GDExtension class). Workspace-level logic (concept event routing, IPC polling dispatch) is tested manually.
• Real PTY spawning is #[ignore] in Rust tests — slow and environment-dependent. Tested manually on Linux and Windows.

Files without automated coverage (manual checklist only):

• godot/scenes/terminal/workspace.gd — restore/sanitize wiring, concept event routing, IPC dispatch (routing patterns are unit-tested via the test_ipc_routing.gd mirror)
• godot/scenes/terminal/terminal_pane.gd — renderer and input paths are partially covered by test_keyboard.gd/test_copy_routing.gd mocks; real rendering is manual-only
• godot/scenes/ui/settings_panel.gd, godot/scenes/ui/pane_settings_panel.gd, godot/scenes/ui/status_bar.gd, godot/scenes/ui/toast_overlay.gd, godot/scenes/ui/icons.gd
• godot/scenes/panes/code_viewer.gd, godot/scenes/panes/file_tree.gd, godot/scenes/panes/inspector_pane.gd, godot/scenes/panes/reasoning_pane.gd — unit-tested for routing/session contracts; real OMP/Markdown rendering is manual
• godot/scenes/autoloads/focus_manager.gd, godot/scenes/autoloads/shortcut_manager.gd, godot/scenes/autoloads/toast_manager.gd, godot/scenes/autoloads/update_checker.gd

Manual pre-release checklist

Run before tagging a release. Requires a built GDExtension library and a running Godot instance.

Setup

cargo build -p gpty-gdext
cp target/debug/libgpty_gdext.so godot/bin/libgpty_gdext.linux.x86_64.so
godot --path godot &

All CLI commands below use the default socket path ($XDG_RUNTIME_DIR/gpty.sock on Linux) or the GPTY_SOCKET env var if set.

IPC bridge — CLI-to-GUI roundtrip

Given the GUI is running with at least one auto-spawned terminal When CLI commands are issued Then the GUI responds correctly

Daemon lifecycle

Given the GUI is running

Standalone commands (no GUI needed)

Error paths

UI regression

Given the GUI is running with at least two panes

Concept engine regression

Given the GUI is running with a terminal pane and default concepts loaded

Platform-specific

Terminal mouse reporting

Given the GUI is running and a pane is in a mouse-aware TUI (nvim, lazygit, htop with mouse on)

Test case format

New manual test cases follow this pattern:

**Given** preconditions (state before the test)
**When** action performed
**Then** expected observable outcome

For CLI commands, include the exact command and expected output format. For UI actions, describe the gesture and the visual change.