Test action events should not be emitted after ending the test

[wentwrong]

We should prevent emitting test action events after the test with corresponding actions has finished.

There are some cases when test action events (test-action-start and test-action-done) can be emitted after the test has already finished running. In one such case it caused an error with BrowserProvider, because eval was placed in a chain with preceding wait action:

await t
    .wait(timeout)
    .eval(() => location.reload(true));

Since the actions preceding eval in this chain are called without await-ing them, the events got desynchronized. The test-action-done event of the wait action was called after the test has already finished and hence browser was closed. The event handler of test-action-done performed call to the isHeadlessBrowser method of the BrowserProvider, which crashed with an unexpected error.

Navigate to the original ticket in order to get the stack trace and reproducible example: Investigate the problem with BrowserProvider caused by extended log reporter.