See astronomy-commons/hats#106
My first instinct when debugging a smoke test is to figure out which dependencies have changed. This is tricky if it requires visually inspecting the pip install logs, and these don't include all dependencies (e.g. numpy).
Also, maybe add something in the CI testing documentation about how to diff the outputs between a successful and failed smoke test run.
See astronomy-commons/hats#106
My first instinct when debugging a smoke test is to figure out which dependencies have changed. This is tricky if it requires visually inspecting the pip install logs, and these don't include all dependencies (e.g. numpy).
Also, maybe add something in the CI testing documentation about how to diff the outputs between a successful and failed smoke test run.