QA/Automation/Projects/Mozmill Shared Modules/API Refactor: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Overview= {| | style="width: 45%" | | style="width: 55%" | |- valign="top" | '''Lead:''' | [mailto:hskupin@mozilla.com Henrik Skupin] |- valign="top" | '''Co-workers:'''...")
 
Line 5: Line 5:
  |- valign="top"
  |- valign="top"
  | '''Lead:'''
  | '''Lead:'''
  | [mailto:hskupin@mozilla.com Henrik Skupin]
  | [mailto:gmealer@mozilla.com Geo Mealer]
  |- valign="top"
  |- valign="top"
  | '''Co-workers:'''
  | '''Co-workers:'''
  | Geo Mealer
  | Henrik Skupin
  |- valign="top"
  |- valign="top"
  | '''Dates:'''
  | '''Dates:'''

Revision as of 19:27, 11 August 2010

Overview

Lead: Geo Mealer
Co-workers: Henrik Skupin
Dates: No end date set
Status: Exploring new ways to present the Shared API to simplify test scripts.
Repository Location: http://hg.mozilla.org/users/gmealer_mozilla.com/mozmill-refactor/
Tracking Bug / Bug List: TBD
Documentation: TBD

Project details

We're exploring different ways to structure and present both Shared APIs and tests. Some values we're optimizing for are:

  • Low learning ramp for writing Mozmill tests
  • Understandable and verifiable test code
  • Repeatable and accurate test runs

Initial ideas center around creating a custom "testing language" by splitting the Shared API into two classes of modules:

  • API modules contain functions for completing complex tasks
  • UI modules contain a map of the Firefox UI used for per-control access.

API modules would be primarily used in setup for tests where fine control isn't needed. UI modules would be used to simulate a QA Engineer running a test.

Some initial ideas for what we're targeting can be found in: