Dance Party timing metrics #25941
Merged
Dance Party timing metrics #25941
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
islemaster
force-pushed
the
test-interface
branch
from
692acd3
to
1b8afc1
Compare
davidsbailey
approved these changes
Nov 9, 2018
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.
Composes timing metrics from the Dance Party app with some code studio-specific timing metrics and makes them available on a test interface.
This is so that our stress tests can easily measure load time and framerate data on a variety of devices.
Depends on code-dot-org/dance-party#227. See also https://github.com/code-dot-org/dance-stress-test/blob/a36eb27aba97e3df12af2a7e5af6037f377c2ee2/tests/DancePage.py#L120-L139.