What problem does it solve? Writing consistent, maintainable Go tests is hard when projects mix pure functions, filesystem operations, TUI state machines, and rendered output. This Skill provides a decision framework that maps each kind of code under test to the right Go testing pattern, so tests stay deterministic, focused, and easy to review. ## Core Features & Use Cases - Pattern Selection via Decision Gates: Maps code under test (pure functions, file operations, TUI state, rendered output, external commands) to the correct test pattern such as table-driven tests, t.TempDir(), direct Model.Update() calls, teatest, or golden files. - Bubbletea and teatest Guidance: Distinguishes when to test Model.Update() directly for state transitions versus when to use teatest.NewTestModel() for full interactive flows. - Golden File Discipline: Enforces deterministic golden files updated only through the repo's -update flag, with a rerun-without-update verification step. - Use Case: While adding a new screen to a Bubbletea CLI, use this Skill to write a direct Update() test for the state transition, a golden file test for the rendered view, and a skippable integration test for the external command it shells out to. ## Quick Start Ask the assistant to write tests for a specific Go function or Bubbletea model following the go-testing patterns, then run the narrow package test before the broader suite.
