Handling testing & validation errors

[myitcv]

Creating a new discussion following an exchange with @kghenderson on Slack:

i wish there were a clearer way to handle testing & validate errors, ideally similarly to the https://onsi.github.io/ginkgo/ method of testing cue files and packages

[myitcv]

Please can you describe what you are looking to test here? Are we talking pure CUE?

[myitcv]

Reply from @kghenderson:

this is for pure cue, but also relates to a whole separate ramble on BDD (behaviour driven development), and how i think that's particularly suited to cue

and how for the people doing that testing/validation (i.e. the '3 amigos'), that pure cue would be a great format (note this also ties in to table support and $after and some other topics)

also the $return/function signature thing and general business & export friendly readability

[myitcv]

Can we make this concrete (no pun intended!) with some example CUE, along with the things you are looking to test?

[myitcv]

cc @rogpeppe who has a love of CUE + testing.