[Bug]: UnitTestRunner should report context

[umlaeute]

Detailed steps on how to reproduce the bug

• trigger a failing UnitTestRunner run (e.g. [Bug]: UnitTestRunner fails when run as root #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:

JUCE/modules/juce_core/files/juce_File.cpp

Lines 1078 to 1090 in 078b1cd

	expect (home.isDirectory());
	expect (home.exists());
	expect (! home.existsAsFile());
	expect (File::getSpecialLocation (File::currentExecutableFile).exists());
	expect (File::getSpecialLocation (File::currentApplicationFile).exists());
	expect (File::getSpecialLocation (File::invokedExecutableFile).exists());
	expect (home.getVolumeTotalSize() > 1024 * 1024);
	expect (home.getBytesFreeOnVolume() > 0);
	expect (! home.isHidden());
	expect (home.isOnHardDisk());
	expect (! home.isOnCDRomDrive());
	expect (File::getCurrentWorkingDirectory().exists());
	expect (home.setAsCurrentWorkingDirectory());

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