Preflight check for a working Temper setup.
$ mix temper.doctor
Runs the checks that catch the mistakes which fail silently:
- is
Temper.Formatterregistered for the test env — proven by the evaluatedconfig :ex_unitvalue or by recorded history? - is
config :temper, history_pathvisible outside the test env, somix temper.reportreads where the formatter writes? - do umbrella child apps declare
:temper, or will app-dir test runs record nothing? - did test runs actually append records to the history?
- do the recorded records carry a usable commit SHA?
Exits with a non-zero status when a check finds a problem, so the doctor can gate setup verification in CI. Warnings do not fail.
Options
--history GLOB— inspect this path or glob instead of the configured or default one. A literal{partition}widens to*