fix(text-editor): move unit tests to playwright #7736
Draft
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.
WIP
Proposed behaviour
The
TestEditorcomponent, which was introduced to support Jest unit tests forTextEditor, has been removed. Tests now useTextEditordirectly or wrap it withLexicalComposerwhere appropriate, while maintaining 100% code coverage.In addition, multiple Playwright tests have been added for
TextEditorto ensure its behavior is validated in a real browser environment. Some of the unit tests that were flaky and not required for the 100% code coverage have been moved to Playwright tests.Current behaviour
Currently, the
TestEditorcomponent is used to support Jest unit tests, however, this approach is not always ideal, as it relies on a simplified version of the actual component. The Playwright tests can be improved to cover more functionality even if there is some overlap with the jest unit tests.Checklist
d.tsfile added or updated if requiredQA
Additional context
Testing instructions