Fixes an issue on running Custom E2E tests when you used both the --woo parameter and --plugin=woocommerce. If you used --plugin woocommerce it would work.
This PR fixes this behavior, and also prevents the user from using both --woo and --plugin=woocommerce, and asks to pick one or the other.
Testing Instructions
Check out this branch
Try to run a test with both --woo <version> and --plugin woocommerce and see that it prevents you from doing that
Check that the self-tests for the custom tests are passing:
PS: You might need to spin up your Manager or deploy trunk to Staging depending on what environment you have in your .env file.
As per Slack https://a8c.slack.com/archives/C03R7A7D1DW/p1718530807725489
Fixes an issue on running Custom E2E tests when you used both the
--wooparameter and--plugin=woocommerce. If you used--plugin woocommerceit would work.This PR fixes this behavior, and also prevents the user from using both
--wooand--plugin=woocommerce, and asks to pick one or the other.Testing Instructions
--woo <version>and--plugin woocommerceand see that it prevents you from doing that.envfile.cd _tests/custom-tests./vendor/bin/paratest