Currently, the CI has a number of steps in CI that perform some lightweight integration tests which all report to GITHUB_STEP_SUMMARY on success. This strategy should be retooled so that failures are also reported. See linked comment below, but I think that there must be a testing framework that solves this problem in a more elegant way than just-a-bunch-of-shell-scripts™️
|
# TODO: nicely formatted summary output doesn't show the failures |
|
# Maybe just write a bunch of shell scripts and exec them here |
|
# Loop over them and report the name ($0), results (✅, ❌) |
.
Currently, the CI has a number of steps in CI that perform some lightweight integration tests which all report to
GITHUB_STEP_SUMMARYon success. This strategy should be retooled so that failures are also reported. See linked comment below, but I think that there must be a testing framework that solves this problem in a more elegant way than just-a-bunch-of-shell-scripts™️PyTerraBackTyl/.github/workflows/docker-build.yaml
Lines 109 to 111 in 3f2e781