QA/Automation/Projects/Endurance Tests: Difference between revisions
< QA | Automation | Projects
Jump to navigation
Jump to search
| Line 43: | Line 43: | ||
=== Phase I === | === Phase I === | ||
# 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 | |||
# A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance | |||
Revision as of 23:24, 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
Phase I
- 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
- Takes a JSON parameter with:
- A 'snippet' that uses the new command line wrapper and outputs results that would potentially expose degradation of performance