QA/Automation/Projects/Endurance Tests: Difference between revisions

From MozillaWiki
< QA‎ | Automation‎ | Projects
Jump to navigation Jump to search
No edit summary
Line 53: Line 53:
#* Outputs memory usage to console
#* Outputs memory usage to console
# A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance
# A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance
=== Phase ? ===
* Output results to a location on the file system
* Read parameters in from disk
* Determine areas of perceived risk with the AUT
* Write more test snippets based on above
* Gather metrics on more system resources
* Present results in an easy to digest way
== Outstanding Items ==
# Endurance Automation Wrapper - This is the harness that will launch the AUT, run the test snippet until either the loop count is reached or the maximum time has elapsed, and report results.
# Initial Test Snippet - The intention is to write a simple test snippet that opens and closes the add-ons manager.

Revision as of 23:50, 14 December 2010

Overview

Lead: Aaron Train
Co-workers: Dave Hunt
Dates: TBD
Status: In process of requirements gathering
Discussion: Etherpad Document
Repository Location: TBD
Tracking Bug(s): TBD
Documentation:

Project Details

We're exploring different ways and or abilities to utilize Mozmill and its testing capabilities to determine if Firefox can sustain the continuous expected load seen through simulated 'real' web usage. These tests would create a simple real world model that employs a high but normal load pattern of actions for the browser in order to determine any potential:

  • Browser performance degradation
  • Crashes

Summary

Endurance Tests

Test Snippet

A test snippet will be one or more actions that can be performed within the AUT written in JavaScript according to the Mozmill specifications.

Phase I

  1. Command line wrapper for Mozmill that:
    • Takes a JSON parameter with:
      • Number of times to loop
      • Maximum duration of test
    • Runs a single 'snippet' according to the above parameters
    • Outputs memory usage to console
  2. A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance

Phase ?

  • Output results to a location on the file system
  • Read parameters in from disk
  • Determine areas of perceived risk with the AUT
  • Write more test snippets based on above
  • Gather metrics on more system resources
  • Present results in an easy to digest way

Outstanding Items

  1. Endurance Automation Wrapper - This is the harness that will launch the AUT, run the test snippet until either the loop count is reached or the maximum time has elapsed, and report results.
  1. Initial Test Snippet - The intention is to write a simple test snippet that opens and closes the add-ons manager.