QA/Mozmill Test Automation/Panorama Testing: 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:'''...")
 
 
(50 intermediate revisions by 3 users not shown)
Line 5: Line 5:
  |- valign="top"
  |- valign="top"
  | '''Lead:'''
  | '''Lead:'''
  | [mailto:hskupin@mozilla.com Henrik Skupin]
  | [mailto:ahughes@mozilla.com Anthony Hughes] (:ashughes)
  |- valign="top"
  |- valign="top"
  | '''Co-workers:'''
  | '''Co-workers:'''
  | Anthony Hughes, Al Billings, Geo Mealer
  | Al Billings (:abillings) <br> Aaron Train (:aaronmt) <br> Dave Hunt (:davehunt)
|-
| '''Community Contributors:'''
| Clay (:uyclay) <br> Adam (:adamFishHook)
  |- valign="top"
  |- valign="top"
  | '''Dates:'''
  | '''Dates:'''
  | TBD
  | Jan 6, 2011 -> TBD H1'2011
  |- valign="top"
  |- valign="top"
  | '''Status:'''
  | '''Status:'''
  | TBD
  | IN PROGRESS -- seeking contributors<br>2 LANDED, 7 ASSIGNED, 1 PENDING, 12 BLOCKED<br>(13.6% COMPLETE)
  |- valign="top"
  |- valign="top"
  | '''Repository Location:'''
  | '''Repository Location:'''
  | TBD
  | [http://hg.mozilla.org/qa/mozmill-tests/file/tip/tests/functional/testTabView http://hg.mozilla.org/qa/mozmill-tests/file/tip/tests/functional/testTabView]
  |- valign="top"
  |- valign="top"
  | '''Tracking Document:'''
  | '''Tracking Document:'''
  | TBD
  | [https://spreadsheets.google.com/ccc?key=0AlroormSQgiRcEFQNVk1QUgzLVRsLXdSb05nQnVqVVE&hl=en#gid=0 spreadsheet], {{bug|629050}}
|-
| '''Developer Tools'''
| [http://mxr.mozilla.org/mozilla-central/source/browser/base/content/test/tabview/ mochitests], [https://wiki.mozilla.org/Firefox/Projects/TabCandy/ project page]
  |}
  |}


Line 26: Line 32:
The Panorama feature of Firefox 4 provides an exciting opportunity for Mozmill testing. Since many of Panorama's UI operations are relatively complex, a black-box tool like Mozmill is optimal for their testing.  
The Panorama feature of Firefox 4 provides an exciting opportunity for Mozmill testing. Since many of Panorama's UI operations are relatively complex, a black-box tool like Mozmill is optimal for their testing.  


So, for the first time, we will be able to work with developers as a major feature is developed and released to create a full testsuite to address both developer needs and QAs. In addition, as a new, UI-intensive feature, Panorama is a perfect testbed for some of the recent team ideas regarding endurance and performance testing.
So, for the first time, we will be able to work with developers as a major feature is designed and released to create a full testsuite that addresses the needs of both QA and Development.
 
In addition, as a new, UI-intensive feature, Panorama is a perfect testbed to develop some of the recent team ideas regarding endurance and performance testing.


=Project Details=
=Project Details=
Line 32: Line 40:


As the specific guidelines for Panorama testing are developed further, this document will be updated.
As the specific guidelines for Panorama testing are developed further, this document will be updated.
== The Tests ==
Please see the [https://spreadsheets.google.com/ccc?key=0AlroormSQgiRcEFQNVk1QUgzLVRsLXdSb05nQnVqVVE&hl=en#gid=0 spreadsheet] for tracking of test automation.
* A test which is ''pending'' is free to take if you want to work on it.
* A test which is ''blocked'' cannot be worked on until another bug is resolved.
* A test which is ''fixed'' has already been developed and landed into the repository.
* A test which is ''assigned'' is currently being developed
Ultimately, if you want to start working on a test, pick from the ''pending'' tests.  To assign a test to yourself, do the following:
* Open the bug report by clicking the bug number link in the spreadsheet
* Click the ''take'' link beside ''Assigned to''
* Make sure the ''Status'' is set to ''ASSIGNED''
* Write a comment stating something like, "Taking this bug"
* In the spreadsheet, set the status to ''assigned'' cell and add your name to the ''Assignee'' cell

Latest revision as of 01:26, 18 March 2011

Overview

Lead: Anthony Hughes (:ashughes)
Co-workers: Al Billings (:abillings)
Aaron Train (:aaronmt)
Dave Hunt (:davehunt)
Community Contributors: Clay (:uyclay)
Adam (:adamFishHook)
Dates: Jan 6, 2011 -> TBD H1'2011
Status: IN PROGRESS -- seeking contributors
2 LANDED, 7 ASSIGNED, 1 PENDING, 12 BLOCKED
(13.6% COMPLETE)
Repository Location: http://hg.mozilla.org/qa/mozmill-tests/file/tip/tests/functional/testTabView
Tracking Document: spreadsheet, bug 629050
Developer Tools mochitests, project page

Excerpt

The Panorama feature of Firefox 4 provides an exciting opportunity for Mozmill testing. Since many of Panorama's UI operations are relatively complex, a black-box tool like Mozmill is optimal for their testing.

So, for the first time, we will be able to work with developers as a major feature is designed and released to create a full testsuite that addresses the needs of both QA and Development.

In addition, as a new, UI-intensive feature, Panorama is a perfect testbed to develop some of the recent team ideas regarding endurance and performance testing.

Project Details

For now, the Panorama project will follow much the same guidelines as the QA/Mozmill Test Automation/Test Writing project.

As the specific guidelines for Panorama testing are developed further, this document will be updated.

The Tests

Please see the spreadsheet for tracking of test automation.

  • A test which is pending is free to take if you want to work on it.
  • A test which is blocked cannot be worked on until another bug is resolved.
  • A test which is fixed has already been developed and landed into the repository.
  • A test which is assigned is currently being developed

Ultimately, if you want to start working on a test, pick from the pending tests. To assign a test to yourself, do the following:

  • Open the bug report by clicking the bug number link in the spreadsheet
  • Click the take link beside Assigned to
  • Make sure the Status is set to ASSIGNED
  • Write a comment stating something like, "Taking this bug"
  • In the spreadsheet, set the status to assigned cell and add your name to the Assignee cell