QA/Browser Technologies/2011-04-21: Difference between revisions
< QA | Browser Technologies
Jump to navigation
Jump to search
m (→Project Status) |
|||
| Line 11: | Line 11: | ||
** Need testcases for feature owners (Fennec 5) | ** Need testcases for feature owners (Fennec 5) | ||
** [https://wiki.mozilla.org/QA/Fennec/Milestones/5.0 Fennec 5 Testplan] | ** [https://wiki.mozilla.org/QA/Fennec/Milestones/5.0 Fennec 5 Testplan] | ||
* Services QA plan | |||
** Engineering proposes weekly pushes to s-c on server and client | |||
** Tracy working on a proposal for testing | |||
* Discussion on Maintaining Litmus tests for all projects | * Discussion on Maintaining Litmus tests for all projects | ||
Revision as of 17:24, 21 April 2011
« previous mtg | Browser Technologies Home | next mtg »
Discussion Items
- Q2 Goals
- Look over near-final draft
- Update personal goals to reflect these. Remember, goals should be measurable!
- Fennec Stuff
- Fennec Full Features list
- Fennec Features by Releases list
- Need testcases for feature owners (Fennec 5)
- Fennec 5 Testplan
- Services QA plan
- Engineering proposes weekly pushes to s-c on server and client
- Tracy working on a proposal for testing
- Discussion on Maintaining Litmus tests for all projects
- Should we clone test-suites for M-c, aurora, beta?
- or just clone test suites for major releases? Q: need a way to indicate which branch the tests are being ran at.
Project Status
- Fennec
- Manual (aakash)
- Automation (martijn)
- Website Compatibility / Device Compatibility (aaront)
- Sync (Tracy)
- Tentative plan for faster train is around a weekly cycle. Client changes in s-c will be handed to QA for testing Mon-Tue. Server side changes will be handed to QA for testing Wed-Fri. Server side doc is here: https://wiki.mozilla.org/Services/Process/ServerReleaseProcess. PM and dev are working on a weekly cycle schedule for the client side. That work in progress is captured here: http://etherpad.mozilla.org:9000/services-client-merge-process
- This weeks server change was a single bug and just required a smoketest. It passed
- Test pilot (tracy)
- Testing 1.2pre builds. This version is almost exclusively the switch to using built Fx doorhanger notifications. We're on version pre3 as I found a couple issues that needed to be addressed. The latest being bug 651138 - The welcome page returns upon each browser start.
- Bug 641597 - Main menu stops working after a while of using Firefox 4 RC1. It may be caused TP. That or TP may be a vector to cause it. I've seen it a few times recently but haven't been able to nail it down.
- There are up to 5 new studies in the works, 3 from outside sources and 2 from with in the TP team.
- Jinghua sent a proposal for study sign-off which I agreed with. However, it is yet to be documented and QA really can't handle the study sign-off load.
- Identity (tracy)
- No UX is planned 'til end of quarter. Need to touch base with jrconlin before this group meets again to work out QA's approach to testing this feature.
- F1 a.k.a "Firefox Share" (Aaron)
- FF Home (Naoki)
- Jetpack (ayan)
- Open Web Apps (ayan, tchung)
- This is still being redefined. Latest i heard, development focus is shifting toward building the Open Web Apps Store.
- Priorities are being reshifted. More later