Force plugin reactivation after tests

[circlecube]

Add and after statement that runs a cli command to activate the plugin - in case there was an issue with the test and the plugin wasn't reactivated via the test. So the remaining tests don't all fail.

This command requires plugin cypress config to add a pluginSlug env var so the command can know which plugin to activate. So we'll need to add that to each plugin.

Edit - to force tests to run again after adding PluginSlug to Bluehost and Hostgator plugins.

[wpscholar]

In the near future, I'd like to replace the npx commands with REST API calls.

[circlecube]

Would we be able to use an API call if the plugin is disabled though?

OOh, I hadn't realized that plugins had been added to the API. I agree, we should get it using this method, since it'd likely be much faster.

https://developer.wordpress.org/rest-api/reference/plugins/#update-a-plugin

[BrianHenryIE]

There are a few NPM packages that have it already written, e.g. https://github.com/tschortsch/cypress-wp-test-utils

[wpscholar]

It looks like that test utility visits the plugin page and activates/deactivates plugins. The REST API would allow us to avoid waiting on extra page loads.

[circlecube]

I've added pluginSlug to all the plugin cypres configs. Then retriggered these tests to make sure they pass now. If all deactivation tests pass here I'll merge and tag a minor release on this module. (I believe BH and HG have some other unrelated tests that fail still but hopefully we can get them fixed elsewhere soon.)