Also run lifecycle hooks (before:run, after:run, before:spec, after:spec) in plugins while in interactive mode

What would you like?

As described in the last comment of issue 6665 the lifecycle hooks before:run, after:run, before:spec and after:spec in a plugin don’t run while in interactive mode. I don’t really get the reasoning behind this choice. Maybe this is hard to do technically. But I would like these events to be triggered when running in any mode.

Why is this needed?

The reason I would like to use these events is to subscribe and unsubscribe to some of my own events that get triggered by my system to do some integration tests. Another use case I would assume is to prep some data or clear some data that is managed by a plugin, so not to use the beforeEach and stuff of the tests themself but from the plugin.

[KrekkieD]

Hi @jennifer-shehane, it works but apparently not for re-runs or when running multiple specs. I’m running v7.3.0

[cameron]

I also find it surprising and disappointing that these events aren’t run when triggering a re-run in the interactive mode (especially a year later). It makes the interactive mode essentially useless if you rely on the hooks for any setup/teardown.

The obvious thing, to me, is to treat any re-run, whether it’s a single spec or all, as a non-interactive run, which should answer all the questions @jennifer-shehane posed above. I dislike any solution that makes the interactive case different from the non — this is not where I want to spend mental energy on extra complexity in my development process.