gravis
commented
8 years ago Hi, thanks for reporting this. We don't have a short-term solution for that, but we'll definitely take your comment into account for a future version. I will update this ticket then.
From what I can see, there's no way of reseting the current update set. Which means that if you are trying to debug your test runner you get longer and longer update commands if your command exits with 0, but if it exits with 1 it won't start.
It would also be helpful if the documentation is expanded/updated since it's really hard to know what the autoupdate command actually does when it runs your tests. Part of this is that it swallows all output, as far as I can see anyways.