3 Typo
source | link

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

Another avenue to investigate would be the TestWatcher class.

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

Another avenue to investigate would be the TestWatcher class.

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

Another avenue to investigate would be the TestWatcher class.

2 added 160 characters in body
source | link

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

Another avenue to investigate would be the TestWatcher class.

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.

Another avenue to investigate would be the TestWatcher class.

1
source | link

If I understand the question, the issue is not so much about parallelized tests as it is about the JUnit runner's policy of reporting failures individually but only reporting successes in aggregate. If you want information successes to be reported individually, I suggest you register a custom RunListener. The RunListener will be invoked each time an event occurs during the test, e.g. when a test starts, when it finishes, and when it fails.