QA SoftVision Team/DesktopAutomation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "TBD")
 
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
TBD
= Management and Communication =
=== Project Updates ===
* Add yourself to the list of [https://wiki.mozilla.org/QA/Mozmill_Test_Automation#Team_Members_and_Assignments Team Members]
* [https://wiki.mozilla.org/QA/Test_Automation#QA_Automation_Weekly_Scrum_Pads Weekly Scrum Pads]
 
=== Meetings ===
* [https://wiki.mozilla.org/QA/Fennec/Waverley#Weekly_Meetings Weekly Waverly] meeting
* [https://wiki.mozilla.org/QA/Test_Automation#Meetings Bi-weekly Desktop Automation] meeting (optional)
 
=== IRC ===
* [http://wbe02.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23mozmill #mozmill] on irc.mozilla.org (use SSL)
 
=== Mailing Lists ===
* [http://groups.google.com/group/mozmill-dev?pli=1 mozmill-dev] - Mozmill Developer mailing list hosted on Google
* Use internal Waverly mailing list to communicate active work to managers
 
=== Bug watchers ===
* '''mozmill-tests@mozilla-qa.bugs''' - Mozmill Tests (''required'')
* '''mozmill-automation@mozilla-qa.bugs''' - Mozmill automation scripts (''optional, but proposed'')
* '''mozmill-crowd-extension@mozilla-qa.bugs'''- Mozmill Crowd extension (''optional'')
* '''mozmill-result-dashboard@mozilla-qa.bugs'''- Mozmill Dashboard (''optional'')
 
=== Spreadsheets ===
* [https://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&pli=1#gid=4 Mozmill Test Coverage] (Send proposed email address to Henrik)
 
= Mozmill =
=== First Steps ===
* Install [https://developer.mozilla.org/en/Mozmill_Tests#Installing_Mozmill Mozmill]
* Get familiar with the handling of our [https://developer.mozilla.org/en/Mozmill_Tests Mozmill Tests]
* Clone the [http://hg.mozilla.org/qa/mozmill-automation mozmill-automation] repository
 
=== Hardware and Environments ===
* It is important to have hardware or VMs available which cover test-runs on all of our supported platforms (Windows, Linux, OS X)
* Test developing should be done on Linux and OS X due to better debugging capabilities
* Use whatever text editor you like
 
= Tasks =
=== Test Creation ===
* Identify areas of work with [mailto:vlad.maniac@softvisioninc.eu Vlad irc: vladmaniac] and [mailto:ahughes@mozilla.com Anthony irc: ashughes]
* Current status in tracked in the [https://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&pli=1#gid=4 Google Spreadsheet]
* Follow the steps as given on the [https://wiki.mozilla.org/QA/Mozmill_Test_Automation/Test_Writing project page]
* Review Process
** Review: Vlad, Alex, Anthony (ask for availability on IRC for a fast process)
** Super-Review: Anthony
 
=== Shared Modules / UI map ===
* If necessary existing shared modules or ui maps have to be enhanced to allow access to specific elements and back-end features of a component
* Review Process
** Review: Henrik, Geo or any other QA Automation services team member
 
=== Fixing broken Tests ===
* Daily checks of our dashboards: [http://mozmill-release.brasstacks.mozilla.com/ daily/release], [http://mozmill-crowd.brasstacks.mozilla.com/ crowd]
* Follow the steps as given on the [https://wiki.mozilla.org/QA/Mozmill_Test_Automation/Fixing_Broken_Tests project page]
* Review Process
** Review: Vlad irc: vladmaniac, Alex irc: AlexLakatos
** Super-Review: Anthony irc: ashughes
 
= Additional Information =
* Henrik will be available throughout the day (European time) to help out at any time
* Automation team members from Softvision will be flexible, so Desktop and WebQA can help out each other
* Each Mozmill test covers exactly one test on Litmus (make sure the test is accurate before starting to work on it - re-check with group owner if necessary)
* When tests have been updated always test them across platforms and with the automation test-run script from the mozmill-automation repository.
* Don't forget to update the Litmus tests which are connected to Mozmill tests of the same Branch
* If you have to disable a Litmus test please follow [https://wiki.mozilla.org/QA/Execution/Litmus#Disabling_of_Litmus_Tests those steps].
* Obey the [https://developer.mozilla.org/en/Mozmill_Tests/Mozmill_Style_Guide Style Guide] for Mozmill tests.
* We do not add new Mozmill tests to older branches, only for Nightly and Aurora. Only test fixes will be allowed to land on older branches.

Latest revision as of 12:42, 4 August 2011

Management and Communication

Project Updates

Meetings

IRC

Mailing Lists

  • mozmill-dev - Mozmill Developer mailing list hosted on Google
  • Use internal Waverly mailing list to communicate active work to managers

Bug watchers

  • mozmill-tests@mozilla-qa.bugs - Mozmill Tests (required)
  • mozmill-automation@mozilla-qa.bugs - Mozmill automation scripts (optional, but proposed)
  • mozmill-crowd-extension@mozilla-qa.bugs- Mozmill Crowd extension (optional)
  • mozmill-result-dashboard@mozilla-qa.bugs- Mozmill Dashboard (optional)

Spreadsheets

Mozmill

First Steps

Hardware and Environments

  • It is important to have hardware or VMs available which cover test-runs on all of our supported platforms (Windows, Linux, OS X)
  • Test developing should be done on Linux and OS X due to better debugging capabilities
  • Use whatever text editor you like

Tasks

Test Creation

Shared Modules / UI map

  • If necessary existing shared modules or ui maps have to be enhanced to allow access to specific elements and back-end features of a component
  • Review Process
    • Review: Henrik, Geo or any other QA Automation services team member

Fixing broken Tests

  • Daily checks of our dashboards: daily/release, crowd
  • Follow the steps as given on the project page
  • Review Process
    • Review: Vlad irc: vladmaniac, Alex irc: AlexLakatos
    • Super-Review: Anthony irc: ashughes

Additional Information

  • Henrik will be available throughout the day (European time) to help out at any time
  • Automation team members from Softvision will be flexible, so Desktop and WebQA can help out each other
  • Each Mozmill test covers exactly one test on Litmus (make sure the test is accurate before starting to work on it - re-check with group owner if necessary)
  • When tests have been updated always test them across platforms and with the automation test-run script from the mozmill-automation repository.
  • Don't forget to update the Litmus tests which are connected to Mozmill tests of the same Branch
  • If you have to disable a Litmus test please follow those steps.
  • Obey the Style Guide for Mozmill tests.
  • We do not add new Mozmill tests to older branches, only for Nightly and Aurora. Only test fixes will be allowed to land on older branches.
Retrieved from "https://wiki.mozilla.org/index.php?title=QA_SoftVision_Team/DesktopAutomation&oldid=336197"