Tui Testing

What it does

This skill automates testing for terminal user interface (TUI) applications, specifically designed for Bubbletea v2 applications based on the hive diff viewer implementation. It facilitates a layered testing approach encompassing unit tests for pure logic, component tests for view behavior, golden file tests for visual regression verification, and integration tests using teatest. The skill provides structure and conventions to ensure thorough TUI functionality and visual correctness across different environments.

When to use it

• Verifying the visual output of a Bubbletea v2 application against known "golden" files (visual snapshots).
• Testing specific features or components within a TUI, such as scrolling behavior.
• Ensuring that data parsing and transformation logic functions correctly without affecting UI state.
• Performing end-to-end workflow testing using teatest.
• Automating regression testing to catch visual changes after code modifications.

Key capabilities

• Layered Testing: Supports unit, component, golden file, and integration tests.
• Golden File Verification: Compares rendered output against predefined "golden" files for visual regression testing.
• Component-Specific Tests: Enables focused testing of individual TUI components.
• Feature-Specific Tests: Allows targeted testing of particular features within a component.
• Naming Conventions: Provides standardized naming conventions for test files and functions.

Example prompts

While this skill is primarily used through code integration, example interactions might include:

• "Run the golden file tests for the diffviewer component."
• "Execute the unit tests for the lineparse module."
• "Perform a visual regression test of the TestDiffViewerView_NormalMode.golden file."

Tips & gotchas

• This skill is tailored to Bubbletea v2 applications and relies on its internal structure.
• Golden files serve as the baseline for visual correctness; ensure they accurately represent the desired output.
• Familiarity with Go testing conventions (using require.* and assert.*) is helpful for writing effective tests.