As discussed in #2623, this change will use the original test class name instead of the test suite name when generating the test output XML when run against a JUnit suite.
I've tried to keep the change as small as possible by overloading the TestCaseSummary constructor to default the new testSuite parameter to false, so that all the other usages of this aren't affected, but if it's better to push this default up to the places where this class is instantiated then I can do that instead!
One thing that CI pointed out to me was that changing the shape of TestCaseSummary caused a unit test to fail because there are checks on how this object serialises. I've updated that test, but I'm not familiar with what the actual implications of changing this are and whether that suggests that maybe I should be achieving this result in a different way.
Also, one CI job is failing but I don't believe that's related to my change.