Integration tests: act
warnings can still be triggered when testing the editor in multiple tests
#38332
Labels
Mobile App - i.e. Android or iOS
Native mobile impl of the block editor. (Note: used in scripts, ping mobile folks to change)
[Type] Bug
An existing feature does not function as intended
Description
In #38052 we identified that some
act
warnings were triggered after the test finishes, we managed to address them by assuring that all timers are run after the editor is initialized. However, I identified that these warnings can still be triggered if you have at least two tests that initialize the editor (check the below example).Warning:
Step-by-step reproduction instructions
act-warnings.test.js
and place it inpackages/react-native-editor/src/test/act-warnings.test.js
and include the code below:npm run native test -- act-warnings.test.js
act
warnings.Expected behaviour
act
warnings shouldn't be displayed when r tests.Actual behaviour
act
warnings are displayed when running tests.Screenshots or screen recording (optional)
N/A
WordPress information
Device information
The text was updated successfully, but these errors were encountered: