test output directory is confusing

[hannesm]

since #125 / #137 was merged, the test output is located at _build/default/test/_build/_tests/UUID/<testname.txt>. This is very hard to navigate to.

In order to read the output of a failing test, I now first have to figure out the UUID of this run, which is sometimes hidden pages above the failing test case. And then I've to navigate to the directory, remembering on the next test run to switch to a different directory again.

I still don't understand the motivation to output into a randomly-generated directory, but if it is useful for others, what about creating a symbolic link when a testrun starts(!!) linking to the current testrun e.g. _build/default/test/current pointing to _build/_tests/UUID/? then there'd at least be a canonical way to read the output!?

[hannesm]

this is even more confusing if you've multiple tests (i.e. test runners, executables) in your project, and now they all output to their own randomised output directory, which means on failure you first have to figure out which uuid + test was failing...