canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,751
edits
QA/Test Automation/2010-09-22: Difference between revisions
Jump to navigation
Jump to search
QA/Test Automation/2010-09-22 (view source)
Revision as of 21:59, 22 September 2010
, 22 September 2010→Meeting Notes
| Line 159: | Line 159: | ||
=Meeting Notes= | =Meeting Notes= | ||
* Last action items | |||
** Limits of the test harness on buildbot to use other local webservers | |||
*** Pretty strict handling for accessing other servers | |||
*** It would be possible to have tests running on a Talos server; Therefore a test environment has to be setup | |||
* Goals Q3 | |||
** We drop the Mozmill crowd extension from our list | |||
** Dashboard will be ready for general test results by end of this week | |||
** Anthony and Aaron will finish the first part of the local test data project | |||
** Henrik updates the AddonsAPI and the existing tests until end of next week (Aaron will help out once the local data project is done) | |||
** Geo will have a solid plan for the refactoring work by end of this month | |||
** Adrian will work on the DOMWalker to have it ready by end of this month | |||
* Goals Q4 (Finalized by next week) | |||
** {{prev| Develop and deploy a Mozmill crowd-sourcing extension that will allow community users to execute and report results of Firefox 4 mozmill automated tests across the available platforms and configurations used by the Mozilla testing community. }} | |||
** {{new|Integrate local data-based Firefox 4 mozmill tests under Buildbot execution control and reporting}} | |||
** {{new|Collaborate with development team to expand Mozmill Panorama support to include an automated test suite for functional and performance testing of the Firefox 4 Panorama feature.}} | |||
** {{new|}} Implement Mozmill Dashboard views for software update and addon tests | |||
** {{new|}} Refactoring the shared module system based on the specification from Q3 | |||
* Others | |||
** Geo: More often conversations about goals and blockers except our 1-1's and the bi-monthly meeting | |||
*** We will setup our own IRC #mozmill channel and have an internal mailing list (qa-auto) | |||
** On demand test execution improvements | |||
*** Geo: Shouldn't be a team goal regarding time constraints | |||
*** Henrik: We can have at least the download script integration | |||
==Action Items== | ==Action Items== | ||
| Line 167: | Line 189: | ||
* Henrik: Talk with John O'Duin about specifics of the test environment | * Henrik: Talk with John O'Duin about specifics of the test environment | ||
* Henrik: Setup IRC channel #mozmill + Mailing list (qa-auto) | * Henrik: Setup IRC channel #mozmill + Mailing list (qa-auto) | ||
* Henrik: Send out goals proposals for final rework | |||
* Matt: {{prev|}} Action items from release tasks meeting? Need to notify release leads that they're responsible for coordinating resources. | * Matt: {{prev|}} Action items from release tasks meeting? Need to notify release leads that they're responsible for coordinating resources. | ||