Added editor initialization manual performance test #6124
Conversation
| HTML payload. | ||
| </div> | ||
|
|
||
| <style> |
There was a problem hiding this comment.
<style> could be moved to the top
| } | ||
| </style> | ||
|
|
||
| <div id="editor_small" class="editor"></div> |
There was a problem hiding this comment.
The <hr> would be nice here as in other manual tests (small issue but would be nice to have same visual pattern for those tests).
| @@ -0,0 +1,8 @@ | |||
| # Performance: editor initialization | |||
|
|
|||
| 1. You might want to enable devtools profiling. | |||
There was a problem hiding this comment.
This steps should describe to other guys how to measure performance (in short). So I'd not use might or optional here - just the steps required to perform the check.
| @@ -0,0 +1,11 @@ | |||
| <div id="test-controls"> | |||
There was a problem hiding this comment.
Those files are mangled from another PR. For atomic PRs we can't create branches from one another (only from master). The problem might be shared code but for those quick PRs we should minimize the round-trip time for review.
ps.: I'll see how this will look after merging #6103.
Suggested merge commit message (convention)
Tests: Added editor setData manual performance test. Part of #5880.
Additional information
File
utils.jswas placed above of manual test directory, as otherwise it was parsed as a manual test and could not be included at all to the test.