Tests: Attemp at a performance test for textinput #661
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
ghost
assigned
tito
added a commit
that referenced
this pull request
Sep 30, 2012
Tests: Attemp at a performance test for textinput
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.
As I needed to see the difference before and after the TextInput fixes I wrote this rudimentary performance test.
I don't know if this is the right approach for writing a performance test, since I have no experience.
Any guidelines/constructive criticism would be much appreciated.
P.S.
It's possible that this tests is only useful for testing the particular improvement that I did and might not be usable for testing textinput performance generally. If so let me know and I will remove the pull.
Update: the output of this test can be looked at here #662