CodeVetter · Repo Unpack · Extension points
gotestyourself/gotestsum
Extension mechanisms are explicit Go interfaces, factories, and command switches. The reusable event parser allows callers to provide readers, callbacks, cancellation, and existing execution state. Reporting and automation extensions fit through formatters, JUnit configuration, and post-run executables. New commands require direct router and help integration.
- Add a tool command through main.toolRun's dispatch switch and usage text, following the existing Run(name, args) interface used by slowest and matrix.
- New terminal formats plug into EventFormatter.Format and NewEventFormatter's explicit factory switch; unknown names return nil and become a command error.
- EventHandler.Event and Err support custom consumers, with an Event error stopping scanning; ScanConfig accepts custom readers, Stop callbacks, RunID, and an existing Execution.
- A caller can omit Handler and Stderr for standalone log parsing; ScanTestOutput supplies a no-op handler and empty stderr reader.
- JUnit Config accepts FormatFunc callbacks for suite names and testcase classnames, with identity defaults; CLI full/relative/short options adapt these callbacks.
- --post-run-command integrates external automation through argument parsing, output writers, report paths, elapsed time, and TESTS_* counters; notification examples consume those counters.
- filewatcher.Watch accepts a run(Event) callback, separating filesystem/keyboard event detection from command execution; Event carries package path, appended arguments, and debug mode.
- ByElapsed accepts a timing-reduction function, slowest supports custom parsed Go statements, and rerunFailsFilter selects either root cases or FilterFailedUnique; these are concrete policy seams for aggregation, rewriting, and retries.