You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have carried out troubleshooting steps and I believe I have found a bug.
I have searched for similar bugs in both open and closed issues and cannot find a duplicate.
Describe the bug
Following the instructions in the README results in a looping in terminal of:
Waiting for testing environment
and in the Docker logs of:
Warning: The package could not be installed. "Your WordPress version is 5.8, however the uploaded plugin requires 5.9."
Warning: The 'woocommerce' plugin could not be found.
Error: No plugins installed.
The WordPress version is defined in node_modules/@woocommerce/e2e-environment/bin/docker-compose.sh.
Solved by editing package.json to "docker:up": "WP_VERSION=6.1 npx wc-e2e docker:up",
Questions/Requests:
@woocommerce/e2e-environment hasn't been updated in almost a year. Is there a way to use @master instead of ^0.3.0? I see woocommerce/woocommerce's .nvmrc is at v16 compared to this repo's v12 so I presume as I learn from the tests in WooCommerce itself they might not work in my project using the older version.
WordPress Environment
No response
Isolating the problem
I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
This bug happens with a default WordPress theme active, or Storefront.
I can reproduce this bug consistently using the steps above.
The text was updated successfully, but these errors were encountered:
Prerequisites
Describe the bug
Following the instructions in the README results in a looping in terminal of:
and in the Docker logs of:
The WordPress version is defined in
node_modules/@woocommerce/e2e-environment/bin/docker-compose.sh
.Solved by editing
package.json
to"docker:up": "WP_VERSION=6.1 npx wc-e2e docker:up",
Questions/Requests:
@woocommerce/e2e-environment hasn't been updated in almost a year. Is there a way to use @master instead of
^0.3.0
? I see woocommerce/woocommerce's.nvmrc
is atv16
compared to this repo'sv12
so I presume as I learn from the tests in WooCommerce itself they might not work in my project using the older version.WordPress Environment
No response
Isolating the problem
The text was updated successfully, but these errors were encountered: