* [http://www.dll-filesdriverskit.com/dllindexdll/downloadmsvcp71.php?msvcp71download0UIgUIXDmS dll/2371.html msvcp71.dll](NOTE: If you have Visual Studio 2003 installed, you've already got it.)

**You need a copy of this file to run Python with all the libraries. **If you have Visual Studio 2003 installed, you've already got it. 

#Make sure the [[Firefox_Performance_Testing_:_A_Python_framework_for_Windows_Documentation#Framework_Prerequisites | prerequisites]] are installed.(sh script will automate this part - but get user to check)

#Download entire framework [http://www.yorku.ca/abel/liz/mozilla/Win32PerfTesting_v4.zip Performance Testing Framework] (directories and all subdirectories) and put it in '''C:\mozilla'''(one of two options 1.put reports dir in the framework 2.check if it exists and prompt user if he/she wants it created)

(Lots of work in this area.. paths.py is unclear, should specify that it can be modified and that these are just defaults.. and the paths are misleading because people think that they are commands for dos) To setup the appropriate paths for the framework, open the '''paths.py''' file in '''cC:\mozilla\testing\performance\win32\''' and configure the paths(CYGWIN, SYNC, BASE_PROFILE_DIR, REPORTS_DIR, INIT_URL, TS_URL, TP_URL):   

*Path Verify that the path is pointing to the desired cygwin directory<pre>CYGWIN = r'c:\cygwin\bin\bash.exe -c'</pre>*The path to cygwin bash to get output from dump() in Firefox*By default, If you didn't specify a different root directory for the Cygwin you just to be installed , it is in your '''C:\ drive''' 

*Run Verify that the path is pointing to the desired cygwin directory<pre>SYNC = r'c:\cygwin\bin\sync'</pre>*Runs sync between Ts runs*By default, If you didn't specify a different root directory for the Cygwin you just to be installed , it is in your '''C:\ drive''' 

*Path to the base profile directory used for testing.*Check Verify that BASE_PROFILE_DIR is pointing to the '''base_profile''' directory*If you didn't alter the dir directory structure, it the '''base_profile''' path would be: ''C:\mozilla\testing\performance\win32\base_profile<pre>BASE_PROFILE_DIR = r'C:\mozilla\testing\performance\win32\base_profile''' </pre>*IMPORTANT: Check that there is content in the '''base_profile ''' directory 

**Set the preference to open new windows in a tab should be off.   

*Path This is the path to the directory that the generated reports will go into*<pre>REPORTS_DIR = r'C:\mozilla\testing\performance\win32\extension_perf_reports'</pre>*Create '''extension_perf_reports''' dir in '''C:\mozilla\testing\performance\win32\'''

**Configure Set '''REPORT_DIR ''' path to a directory where you want the reports to go into. Make sure that directory is created. 

*Path The path to the file url to load when initializing a new profile<pre>INIT_URL = 'file:///c:/mozilla/testing/performance/win32/initialize.html'</pre>

*'''Note: Don't change the local file url to a file path <pre>INIT_URL = 'file:///c:/mozilla/testing/performance/win32/initialize.html'</pre>' 

*The path to the file url to load for page load test (Tp) <pre>TP_URL = 'file:///c:/mozilla/testing/performance/win32/page_load_test/cycler.html'</pre>

*'''Note: Don't change the local file url to a file path ''' =Config file=  <pre>TP_URL = =Config info==(refer to Exended Progress Chart for yaml details - a few things have to be highlighted and clarified) In ''file:///c'C:/\mozilla/\testing/\performance/\win32/page_load_test/cycler.html\'''</pre> Create , create a YAML config file (config.yaml) with info about the profiles you want to test. Copy , paste and paste '''modify''' the following into in config.yamlor refer to [[sample.config]]:

==Instructions==1. Verify that the '''firefox''' path is pointing to the right Firefox instance on your system.* You will hit a zero division error and some other errors if you don't point it to the right path 2. '''preferences''':* If you don't have '''preferences''', change to: <pre>preferences : {}</pre> (make sure there is a space between ":" and "{" or else it will cause a syntax error)* If you do have '''preferences''', refer to [[sample.config]] 3. '''extensions''':* If you don't have '''extensions''' to install, change to: <pre>extensions: {}</pre> (make sure there is a space between ":" and "{" or else it will cause a syntax error)* If you do have '''extensions''' to install, refer to this sample:<pre> extensions: # Make sure that the path is directed to the desired location of the extension # Need quotes around guid because of curly braces "{12345678-1234-1234-1234-abcd12345678}" : c:\path\to\unzipped\xpi foo@sample.com : c:\path\to\other\unzipped\xpi </pre>* Make sure that the path to the extension is right 4. Change '''filename''' and '''title''' to whatever you desire 5. Run In '''cmd''', run '''run_tests.py''' with the name of your config file as an argumentin '''c:\mozilla\testing\performance\win32\''': <pre>$run_tests.py config.yaml</pre> * Running the test will close any existing Firefox windows. (this part has to be highlighted)**You might run into this message on your browser: '''This page should close Firefox. If it does not, please make sure that the dom.allow_scripts_to_close_windows preference is set to true in about:config''' **Type '''auto:config''' in the address bar and double click on '''dom.allow_scripts_to_close_windows''' to change it to true* If you see '''processing... Performance Testing is starting''', performance testing is running.. wait.. * After the performance testing is done, your reports will be placed in the [[Firefox_Performance_Testing_:_A_Python_framework_for_Windows_Documentation#REPORTS_DIR | '''REPORTS_DIR''']] directory you specified in '''paths.py''' *You can use a space-separated list of config files, to generate a report of startup and page load times. The report will be placed in the REPORTS_DIR directory you specified in paths.py.

*This directory contains the JavaScript files and html data files for the page load test. *The page load test opens a new window and cycles through loading each html file, timing each load. 

*This directory contains the JavaScript to run the startup test. *It measures how long it takes Firefox to start up.  ==extension_perf_report/==*This directory is where the generated report will go into. *You may specify another directory to substitute this directory, but make sure that the '''paths.py''' is changed to point to it.

*These files should be configured to run the test on different machines, with different extensions or preferences. See setup above.