This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
forked from adobe/brackets
-
Notifications
You must be signed in to change notification settings - Fork 0
Performance Tests Procedure
peterflynn edited this page Sep 18, 2012
·
19 revisions
Sprint DoD has a task for logging performance tests results. We have a small set of performance tests that run within the unit test window. Eventually these tests will be automated. For now, here are the instructions for logging the sprint performance results:
- Confirm you have edit access to Brackets Performance Tests (Google Spreadsheet). If not, ask @jasonsanjose.
- Get the performance laptop (get key from @pflynn's desk)
- Uninstall any existing Brackets, and install the new Brackets build
- Sync the brackets repo on the machine to match the SHA of the installed build (look for the version field in \www\package.json) (note: you may need to open the SSH tunnel to update from GitHub)
- Run
tools\setup_for_hacking
- Delete the Cache Folder
- Reboot the computer
- Run Brackets
- Debug > Show Performance Data
- Log cold startup time under "Startup > Cold Startup (first run, no prefs)"
- Debug > Run Tests, Performance, All
- Log "Performance Tests File open performance" under "Cold - Performance Tests File open performance"
- Log the first set of "JavaScript Inline Editor Creation" results under "Cold - JSQuickEdit Performance site should open inline editors."
- Log the last set of "JavaScript Inline Editor Creation" results under "Warm - JSQuickEdit Performance suite should open inline editors."
- Exit and restart Brackets
- Debug > Show Performance Data
- Log warm startup time under "Startup > Warm Startup"