Difference between revisions of "New Firefox Performance Testing Documentation"
(→Run Firefox Performance Tests) |
(→Run Firefox Performance Tests) |
||
Line 42: | Line 42: | ||
<b>Cygwin</b> | <b>Cygwin</b> | ||
<pre>./run_tests.py config.yaml</pre> | <pre>./run_tests.py config.yaml</pre> | ||
+ | ==What the script does== | ||
+ | *Creates directories needed for the performance testing | ||
+ | ** Directory that holds the files for the performance testing | ||
+ | ** Reports directory to hold the results generated | ||
+ | *Downloads and installs pre-requisites | ||
+ | *Write to config.yaml |
Revision as of 02:40, 14 December 2006
Contents
Introduction
This documentation is still in progress.
Cygwin Setup
- Cygwin
- Download cygwin.
- Install cygwin with the DOS-style line endings.
- At minimum, you are required to have the following additional tools:
- unzip (Archive category)
- wget (Web category)
unzip (Archive category)
wget (Web category)
Note: For some reason, we can't get output from Firefox unless it's wrapped in a Cygwin sh shell. So we use cygwin for that, and to sync between Firefox runs.
Configuration
Save the script
- Save this script at a desired location
- Edit the script to your own choosing. You may provide a list of extensions to install and test in the config.yaml section.
- Note: This script will run the performance testing. If don't wish for that to happen, simply comment out the last line of the script (to comment out, use #):
#./run_tests.py config.yaml;
Run the script
- In cygwin, browse to the location where you saved your script.
- From cygwin, run the script.
For example:
$./perfconfig.sh
Run Firefox Performance Tests
- By default, the run_tests.py file that you need to execute to run the Firefox Performance Testing is located at c:\mozilla\testing\performance\win32\
- You can run run_tests.py either from the DOS prompt or Cygwin:
DOS
$run_tests.py config.yaml
Cygwin
./run_tests.py config.yaml
What the script does
- Creates directories needed for the performance testing
- Directory that holds the files for the performance testing
- Reports directory to hold the results generated
- Downloads and installs pre-requisites
- Write to config.yaml