Given a Makefile based setup, how to interop with Unity best?

[verdverm]

I'm wondering if there is a way to add Cuetorials GitHub to Unity without having to duplicate everything into testsuite. Basically the commands, inputs, and golden outputs are already on disk, so I would like to avoid having their content duplicated, as well as the commands if possible.

The existing setup is:

• Makefiles to recurse and verify code examples
• Only need make, go, cue, and diff commands to be available

Would it be possible to add a txtar file like this

make verify_code

and have unity rely on the exit code for validation?

Would it be better to have them relatively independent for performance reasons?

I'd like to make sure I set this up to be as beneficial for CUE as possible, so if that means writing txtar files like

exec cue export file.cue > output.cue
cmp stdout expected.cue

(where file.cue and expected.cue are already in the repository)

or a large txtar file like

make -C code/introduction
make -C code/overview/foundations
make -C code/go-api/basics/context
make -C code/go-api/basics/errors
...

Maybe this doesn't make sense because testsuite runs in temp dirs?

---

• top-level Makefile
• mid-level CUE Makefile and mid-level Go Makefile
• low-level CUE Makefile and low-level Go Makefile