Right now, the only way to verify that changes to Tast don't break its end-to-end behavior is by manually running tests using "tast run" and verifying their output. I'm planning to add "meta" tests that themselves run the tast command and check its output.
There's a risk that a change to Tast could break it in such a way that it doesn't report these tests as failing, but I think that it's unlikely. (Also, it seems weird to write an Autotest test to verify that Tast works.)
Comment 1 by bugdroid1@chromium.org
, Aug 14