QA/Execution/Meetings/2008-01-31: Difference between revisions

Latest revision as of 18:44, 1 February 2008

« previous mtg | index | next mtg »

Meeting Agenda:

Automation UI wishlist (al, everyone)
- Discussion - we want this cause it saves time during testing
- be great to automate our bfts, we need this because only eggplant is the only way to do this. we have nothing that can cover our chrome. eggplant is a lot of work, and moving to BFT level. Its great for repetitive work. Also can't run locally- and need a lab setup.

Requirements
- something that is easy for repetitive work. Framework should be flexible for changes.
- GUI driven test tool
- Cross-platform, can drive buttons
- Allow for keystrokes
- run locally on machine, not needing a lab
- community enabled to write testcases
- should have APIs to hook into. perhaps an extension?
- should not be based on image comparison. (eg. look at the DOM), great for accessibility
- some sort of easy, common script-language support (javascript, python?)
- Should be able to run against a normal nightly build
- should have a framework that can categorize folders, tags, etc.. easy enough for QAE members to create libraries
- some sort of record/playback feature
- returning results of the testcase pass/fail. integrate results into litmus?
- incorporated into build process
- one option is to have eggplant cover UI comparisons, but have this tool check for others side
- integrate results into litmus? do pass/fail there?
- able to be packaged independently for downloading

Scheduling and Tasks Prioritization (timr, tchung)
- Suggestions on better communication across teams?
- Discussion - have monthly meetings across teams, talk about projects, whats coming up for each team. right now no one knows who is working on what
- QA project leads need to be clear on who's working on what during the project time. More proactive in getting word out earlier.
- For projects that we do know about, we need to sync up more regularly. For projects that come down the pipe suddenly, how do we resolve this?
  - For now, contact Tim for major project prioritizations. If its organizational, it goes to Tim first to be sure scheduling is appropriate.
- Should have a tracking QA intranet wiki for: (maintained by timr)
  - who's working on what for each quarter
  - Who owns what areas (move this to QMO)
  - Scratchpad section on new areas, unowned
  - maybe use bugzilla to track project requests

Fx3 b3 status - builds Feb 4th (tchung)
- Test plan. Look over your assignments
- Critical beta3 list. Add your concerns here.

2.0.0.12 update (al)

Leak testing update (tomcat)

Webdev update (stephend)
- No update

Community Project update (jay)

Testday this week on 2.0.0.12. Future testdays topics and moderator discussion (tchung, tomcat, tracy)
- Addons Manager testday (new AMO integration pane)
- Download Manager testday
- Themes - Proto and Icon Refresh Testday
- History and bookmarks Testday
- New Places UI testday (would include DnD operations)
- Security testday (cover mostly UI based work, web compatibility)
- Content Handling Testday
- Printing Testday
  - Discussion - have pairs in there 4 hours a day, drumming up conversations, shooting out bugs to help. need to get more interaction going
  - is Friday really the best testday? Jay to requery community to ask them.

Other topics?

@@ Line 4: / Line 4: @@
 * Automation UI wishlist (al, everyone)
+** '''Discussion''' - we want this cause it saves time during testing
+** be great to automate our bfts, we need this because only eggplant is the only way to do this.  we have nothing that can cover our chrome.  eggplant is a lot of work, and moving to BFT level. Its great for repetitive work.  Also can't run locally- and need a lab setup.
+* ''Requirements''
+** something that is easy for repetitive work.  Framework should be flexible for changes.
+** GUI driven test tool
+** Cross-platform, can drive buttons
+** Allow for keystrokes
+** run locally on machine, not needing a lab
+** community enabled to write testcases
+** should have APIs to hook into.  perhaps an extension?
+** should not be based on image comparison.  (eg. look at the DOM), great for accessibility
+** some sort of easy, common script-language support (javascript, python?)
+** Should be able to run against a normal nightly build
+** should have a framework that can categorize folders, tags, etc..  easy enough for QAE members to create libraries
+** some sort of record/playback feature
+** returning results of the testcase pass/fail.  integrate results into litmus?
+** incorporated into build process
+** one option is to have eggplant cover UI comparisons, but have this tool check for others side
+** integrate results into litmus?  do pass/fail there?
+** able to be packaged independently for downloading
 * Scheduling and Tasks Prioritization (timr, tchung)
 ** Suggestions on better communication across teams?
+** '''Discussion''' - have monthly meetings across teams, talk about projects, whats coming up for each team.  right now no one knows who is working on what
+** QA project leads need to be clear on who's working on what during the project time.  More proactive in getting word out earlier.
+** For projects that we do know about, we need to sync up more regularly.  For projects that come down the pipe suddenly, how do we resolve this?
+*** For now, contact Tim for major project prioritizations.  If its organizational, it goes to Tim first to be sure scheduling is appropriate.
+** Should have a tracking QA intranet wiki for: (maintained by timr)
+*** who's working on what for each quarter
+*** Who owns what areas (move this to QMO)
+*** Scratchpad section on new areas, unowned
+*** maybe use bugzilla to track project requests
 * Fx3 b3 status - builds Feb 4th (tchung)
@@ Line 30: / Line 60: @@
 ** Content Handling Testday
 ** Printing Testday
+*** '''Discussion''' - have pairs in there 4 hours a day, drumming up conversations, shooting out bugs to help. need to get more interaction going
+*** is Friday really the best testday?   '''Jay''' to requery community to ask them.
 -----
 * Other topics?