Template Parts: Add unit tests for template part creation functions #47224
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: -5 B (0%) Total Size: 1.33 MB
ℹ️ View Unchanged
|
Co-authored-by: Robert Anderson <robert@noisysocks.com>
|
Flaky tests detected in cef314b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/3944325858
|
juanmaguitar
added
the
[Type] Code Quality
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Follow up to #47082 that adds unit tests for
getUniqueTemplatePartTitleandgetCleanTemplatePartSlug.Why?
To make sure these are working correctly. :)
How?
Some pretty basic Jest unit tests in
packages/edit-site/src/utils/test/.Testing Instructions
Run
npm run test:unit packages/edit-site/src/utils/test/template-part-create.jsand you should see these tests pass: