What problem does it solve? Writing consistent, maintainable Go tests is hard when teams mix patterns, test implementation details instead of behavior, or mishandle TUI and golden-file scenarios. This Skill provides a decision framework that maps each testing target to the right Go testing pattern. ## Core Features & Use Cases - Pattern Selection via Decision Gates: Maps test targets (pure functions, file operations, TUI state, rendered output, external commands) to the correct pattern such as table-driven tests, t.TempDir(), direct Model.Update() calls, teatest, or golden files. - Bubbletea/TUI Testing Guidance: Distinguishes when to test Model.Update() directly 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 verification runs afterward. - Use Case: When adding coverage to a Go CLI with a Bubbletea interface, load this skill to decide whether a screen transition needs a direct Update() test or a full teatest flow, then follow the execution steps to write, run, and verify the tests. ## Quick Start Ask the assistant to write tests for a specific Go function or Bubbletea model using the go-testing patterns and report which scenarios and commands were covered.
