[Bug]: UnitTestRunner should report context

Detailed steps on how to reproduce the bug

• trigger a failing UnitTestRunner run (e.g. #1724 )
• wonder what the following means
  复制

   Starting tests in: Files / Writing...
   !!! Test 47 failed

What is the expected behaviour?

it would be great if the test report could give me a bit of context where to look for the problem. "Test 47" is really very generic, and i find myself walking a file, manually counting expect() lines: https://github.com/juce-framework/JUCE/blob/078b1cd6110e974698dbb4c7e5151d16b08dde9b/modules/juce_core/files/juce_File.cpp#L1078-L1090

i would wish for:

• the filename and line number where the failure was triggered
• the arguments to expect() (probably nicely formatted, as in: expected 0 but got 10)

Operating systems

Linux

What versions of the operating systems?

Debian

Architectures

x86_64

Stacktrace

Plug-in formats (if applicable)

No response

Plug-in host applications (DAWs) (if applicable)

No response

Testing on the develop branch

I have not tested against the develop branch

Code of Conduct

• I agree to follow the Code of Conduct