Eg, a test that takes in some files, and compiles them into reasonable output. Similar for scrimmages.
We could add the input/output files to the repo as well, so that we're merely testing the Go part of the stack.
(If that's difficult, Even a test that, like, spins up the machines and does nothing with them is fine.)
This would give us more confidence that our changes to Go work. Currently, you can only debug / test easily in prod
Eg, a test that takes in some files, and compiles them into reasonable output. Similar for scrimmages. We could add the input/output files to the repo as well, so that we're merely testing the Go part of the stack. (If that's difficult, Even a test that, like, spins up the machines and does nothing with them is fine.)
This would give us more confidence that our changes to Go work. Currently, you can only debug / test easily in prod