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

From MozillaWiki
< QA‎ | Automation‎ | Projects
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 46: Line 46:
= Roadmap =
= Roadmap =


== Phase I - Planned Q1 2011 ==
== Phase I - Planned Q1/2011 ==


# Command line wrapper for Mozmill that:
# Command line wrapper for Mozmill that:

Revision as of 17:59, 12 January 2011

Overview

Lead: Dave Hunt
Co-workers: Aaron Train
Henrik Skupin
Geo Mealer
Dates: Kick-off: December 2010
Phase I: Q1/2011 (goal)
Status: Requirements gathering / planning
Discussion: Etherpad Document
Repository Location: TBD
Tracking Bug(s): TBD
Documentation: TBD

Meetings

Week of 01/10/11

Summary

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 will ultimately 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

Initially, this project will focus on setting up an environment employing a new test harness that will loop through simple test snippets to expose the above areas of concern within Firefox.

Definitions

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.

Roadmap

Phase I - Planned Q1/2011

  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 file
  2. A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance

Phase ?

  • Gracefully handle the AUT crashing, and ensure all reports are intact
  • Output results to a location on the file system
  • Read parameters in from disk
  • Determine areas of perceived risk within the AUT
  • Write more test snippets based on above
  • Gather metrics on more system resources
  • Present results in an easy to digest way
  • Automate the running of endurance tests
  • Abort tests that exceed predetermined resource thresholds
  • Determining saturation points (baselines) in the AUT and monitor for major discrepancies

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.
  2. Initial Test Snippet - The intention is to write a simple test snippet that opens and closes the add-ons manager.

Additional Requirements

  • Use debug nightly builds of Firefox to be able to get a full stack of information