Today’s release prints useful feedback to stderr when Yeti is used in CI. It also includes a fix for issue #74 (Unable to serve error) and #68 (improve DOH support).
When using Yeti to in CI, e.g. to produce JUnit XML output, previous versions of Yeti would go silent after testing began as Yeti produced XML output on stdout. This made it difficult to determine if Yeti was doing anything while tests ran. When using Yeti with
--junit, today’s release prints status after every test completion to stderr while XML prints to stdout.
Big thanks to @henryqdineen for contributing the fix for DOH support!
Expect more updates soon. Code coverage is next on my list.