Tests: Expand JavaScript unit tests for field bindings #330
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.
What
Part of #315.
Expands JavaScript unit test coverage for the block bindings module (
assets/src/js/bindings/).Why
Block bindings enable connecting SCF fields to WordPress block attributes. These utilities handle field processing, metadata caching, editor context detection, and binding source registration. Tests ensure the binding system works correctly across post and site editors.
How
Adding 70 tests covering:
New test files:
block-editor.test.js- HOC filter registration and module setupconstants.test.js- BLOCK_BINDINGS_CONFIG structure and field type mappingsExpanded test files:
field-processing.test.js- All field types with parameterized tests, full branch coveragehooks.test.js- Cleanup/cancellation, null handling, template edge casessources.test.js- canUserEditValue, registration validation, edge casesNote:
block-editor.jshas low coverage because the HOC requires a full React rendering environment with WordPress data stores.Testing Instructions
Run the test suite:
npm run test:unit -- --testPathPattern="tests/js/bindings"