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
We have a report that the wp-env unit tests will fail if your repository directory is not named gutenberg. The problem stems from the many uses of relative paths in config/test/parse-config.js.
Step-by-step reproduction instructions
Rename your Gutenberg directory
Run npm run test:unit packages/env, they should fail
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered:
Since none of these require reading from any real config file, there's not really a reason to have real paths either. We can replace all of the relative paths in the test file with fake absolute paths. This has the added benefit of simplifying all of the tests too.
Description
We have a report that the
wp-env
unit tests will fail if your repository directory is not namedgutenberg
. The problem stems from the many uses of relative paths inconfig/test/parse-config.js
.Step-by-step reproduction instructions
Gutenberg
directorynpm run test:unit packages/env
, they should failScreenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: