QA/Automation: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 15: Line 15:
<small>[[QA/Test_Automation/LastMeeting|Last]] | [[QA/Test_Automation/NextMeeting|Next]]</small>
<small>[[QA/Test_Automation/LastMeeting|Last]] | [[QA/Test_Automation/NextMeeting|Next]]</small>


* [[QA/Test_Automation/2010-10-06|2010-10-06]]
* [[QA/Test_Automation/2010-09-22|2010-09-22]]
* [[QA/Test_Automation/2010-09-22|2010-09-22]]
* [[QA/Test_Automation/2010-09-08|2010-09-08]]
* [[QA/Test_Automation/2010-09-08|2010-09-08]]

Revision as of 13:16, 6 October 2010

Summary

The test automation team is driving the automation efforts by co-working with Test-Dev to enhance the Mozmill functional testing framework, and in automating manual tests to increase the test coverage on all platforms and localized builds of Firefox.

Projects Page: Mozmill Test Automation

Meetings & Notes

Dial in:

 Every other Wednesday at 1:30pm PDT
 
 # 650-903-0800 or 650-215-1282 x92 Conf# 315 (US/INTL) 
 # 1-800-707-2533 (pin 369) Conf# 315 (US) 

Notes:

Last | Next

Team

Mozmill Tests
  • Lead: Henrik Skupin
  • Geo Mealer
  • Al Billings
  • Anthony Hughes
  • Aaron Train
  • Adrian Kalla
  • Marco Zehe
Automated Test-runs
  • Lead: Henrik Skupin
Reporting
  • Lead: Henrik Skupin
Documentation
  • Lead: Henrik Skupin
  • Anthony Hughes

Task Assignments

With a couple of members in the team a strategy is needed for assignments of members to a given set of tasks. Machines which are necessary to execute those tasks, have to keep free during those windows.

Release Testing

  • BFT testrun: Henrik Skupin (European Time), Geo Mealer (West Coast Time)
  • Update testrun: Anthony Hughes