In Pharo 5, it was possible to do...
TestCase subclass: #Example
Example >> test1
crShow: Processor activeProcess priority printString;
show: Processor activeProcess name.
crShow: Processor activeProcess effectiveProcess priority printString;
show: Processor activeProcess effectiveProcess name
] forkAt: 39 named: 'TEST'.
...and when this was run, a debugger would show for the forked code
and stepping through it would produce the following output...
In Pharo 71047, no debugger shows up,
and you only get one...
I guess this because more cleanup of tests is being done,
but it makes it harder to debug multi-threaded tests when
debugger can't replicate the way the code normally runs.