From MozillaWiki
< QA‎ | Platform‎ | DOM
Jump to: navigation, search

This page documents the various metrics QA uses to assess the quality of Firefox/Gecko's DOM implementation from version to version. The purpose of these metrics is to help us make informed decisions about testing strategy. These metrics serve several needs, including but not limited to:

  • identifying areas of risk for testing before we release a new version of Firefox
  • informing root cause analysis discussions when something inevitably slips through the cracks
  • measuring the trends in product quality over the long-term
  • measuring competitiveness and spec compliance

Please contact Anthony Hughes if you have any questions or feedback regarding this initiative. He can usually be found in #qa on between 09:00 and 17:00 (UTC-9/-10) Monday to Friday by mentioning the nickname ashughes.

Phase I: Establishing a Baseline

The goal of the initial phase is to establish a baseline that all future quality can be measured against.

In implementation we will experiment with a lot of different metrics and data sources in an attempt to see which metrics, either singularly or in conjunction with other data, enable us to effectively make informed decisions.


The following metrics were developed using data from Kyle Lahnakoski's elastic search Bugzilla database. Pending peer review, the next step will be to evaluate better charting and eventually a more automated solution.

Pending Investigation

Draft proof of concepts can be found in my Google Drive

Bugzilla Data

Using Manual Querying

Using Elastic Search