-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added editor setData manual performance test #6103
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've forgotten to start a review but only one comment. The (optional)
step doesn't look like optional for testing performance :) We cannot have those only on a "gut feeling".
Co-Authored-By: Maciej <[email protected]>
Co-Authored-By: Maciej <[email protected]>
Ture, the only case when you can gut tell this are these "omg it takes so long that I'm going to take a coffee" kind of cases, which luckily I'm not aware of in our editor 😄 |
Suggested merge commit message (convention)
Internal: Added editor setData manual performance test. Part of #5880.
Additional information
In this micro PR I added a manual test for calling setData on the editor.
Fixtures (so the data that we consider small/medium/large) are extracted as separate files to keep it DRY. Fun fact, it couldn't be
.html
file as it would not be served by our Karma/Webpack config so I went with.txt
. Fixtures contain a dummy placeholder as setting it with proper content will be done in another PR.