It will be helpful during investigating test failures, especially for flaky tests, if we will always know which events were triggered by the driver regardless these events were required by the test itself or no. I've initially implemented this logic in this branch via adding additional EventCapturer on LoggableTestClass level and then always configuring this eventSubscriber as additional event capturer on the DriverTestConfiguration level. So as long as the test has been failed, we will see all triggered driver logs in the format similar to described here. See "Enumerating events". The final events format is open question for now.