Issue-143: Fix Jest bugs #169
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #143
This pull request attempts to ensure Jest works seamlessly after configuration. It includes bumps to dependencies for testing React and WordPress block editor components.
Note
Unfortunately, I was unable to test this directly due to the work in #158 to remove tests (Thanks to @kevinfodness for the sample tests... provided: (1) there is an appropriatenpm run test
via turbo will find no acceptable tests to run with the current configuration).npm run test
script within the theme/plugins and (2) there are items to test, jest tests are confirmed working.Changes
@testing-library
packages to the latest versions and updated other related dependencies to ensure compatibility.react
andreact-dom
at version 18 to resolve peer dependency issues with@testing-library
.jest-environment-jsdom
to ensure DOM-related tests work correctly, as it is no longer included by default in Jest 28+.@testing-library/dom
identity-obj-proxy
to mock CSS, LESS, SCSS, and SASS imports in tests.ts-jest
for native TypeScript compatibility.ts-node
is explicitly required for development and Jest configuration.