Firefox Performance Testing Lab Fall 2010

From CDOT Wiki
Revision as of 10:47, 17 September 2010 by Peleaning (talk | contribs) (Tests)
Jump to: navigation, search


The goal of this lab is twofold. First, to provide students with a real-world experience of working collaboratively in an open community; and second, to work on a cutting-edge, but manageable project within the Mozilla community.


To conduct A/B performance tests of the Chrome Experiments using nightly builds of both Firefox and Chrome, in order to identify performance bottlenecks in Firefox. Also, to profile and file bugs in order to fix these issues.


  • As a group determine a method for dividing the Chrome Experiments so they all get tested
  • Install both the Firefox and Chrome nightly builds
  • Test each experiment in the two browsers, looking for various issues:
    • Speed - is Firefox as fast as Chrome at rendering the graphics?
    • Smoothness - are the graphics as smooth as in Chrome? Do you notice a lot of pauses, jerkiness, etc.?
    • Responsiveness - does Firefox remain responsive while you run the demo? Is it pegging your CPU(s)?
  • Record your findings, as well as browser and computer info ([about:support], [about:]) in the Results Spreadsheet.



(humph) Let's refine this a bit more, such that we track:

Name of Experiment | URL of Experiment | Your Name | Date of Test | Hardware Info | Browser Info | Firefox Performance - Speed | Firefox Performance - Smoothness | Firefox Performance - Responsiveness | Notes and other Details |

(carl) Separate or cumulative results page?

Test No. Name
1-10 Carl Results
11-20 Kevin Lasconia Results
21-30 Andrew Condinho Results
31-40 Stephen Bologna Results
41-50 Kenneth Pangilinan Results
51-60 Pete Leaning Results
61-70 Brian Law Results
71-80 Steven Weerdenburg Results
81-90 James Evangelista Results
91-100 Kaitlyn Callow Results
101-110 Crystal de Nobrega Results
111-120 Chris DeCairos Results

Bug Reports

NOTE: All bugs related to what we find should have [chromeexperiments] in the bug's Whiteboard field, so we can track them. The following Bugzilla search will list them all:[chromeexperiments]