You still do get the results at the end, you just have to wait until
everything is complete.
It isn't too bad so long as you use filter to only run the tests you
actually want to test.
Something else that might be reasonable, so long as all the JSession tests
are in one class (which I didn't look to check) would be to end output
buffering in the tearDownAfterClass so that you would get the normal
progress report as soon as the session tests were done.
Anyway, just thoughts.