It would be helpful to give more consideration to providing useful information to the developer when a test is executed (or fails ideally) about what might have gone wrong with the test.
One idea is to allow the ability to turn logging on at the assertion level instead of at a global level. Global level logging produces too much output and takes too much time; therefore, if there's a specific test that is failing, it would be good to get useful information regarding just that one test.
Maybe this, or other ideas, can be explored to help solve this problem.
It would be helpful to give more consideration to providing useful information to the developer when a test is executed (or fails ideally) about what might have gone wrong with the test.
One idea is to allow the ability to turn logging on at the assertion level instead of at a global level. Global level logging produces too much output and takes too much time; therefore, if there's a specific test that is failing, it would be good to get useful information regarding just that one test.
Maybe this, or other ideas, can be explored to help solve this problem.