QA/Fennec/Waverley/2011-07-19: Difference between revisions

← Older edit

QA/Fennec/Waverley/2011-07-19 (view source)

Revision as of 15:41, 19 July 2011

3,314 bytes added , 19 July 2011

→‎Take Aways This Week

Jbecerra

canmove, Confirmed users

7,810

edits

@@ Line 3: / Line 3: @@
 == Welcome ==
 <i> (eg. headcount, updates with staffing, vacation/away time) </i>
+*Vacation/Away time
+**Teodosia would like a day off on the 22nd of July
 == Take Ways From Last Week ==
@@ Line 16: / Line 18: @@
 * Mozilla (test lead)
 ** Fx8: Pick new features as they come in.
-* Waverley (tester)
+* Waverley (Andrei, George, Simona, Vlad G)
+**No Dev Tools meeting last week
+**Test plan
+***Firefox 6.0 Beta 2
+****Smoketests - [http://mzl.la/pfTCdj Wiki-page]
+****BFTs on WinXP - [http://mzl.la/nFnzR9 Wiki-page]
+****BFTs on Mac OS X 10.7
+****Fixed Bug verification from pushlog - [http://bit.ly/r9AFhf Spreahsheet]
+***Fixed bug verification across platforms - [http://bit.ly/iwrNhI  Spreadsheet]
+***Logged issues - [http://bit.ly/oyCCzX Bugzilla query]
+***Bug triage - [http://bit.ly/e0wiuz Spreadsheet]
+***Updated testcases in Litmus - [http://bit.ly/kJBMUv Spreadsheet]
+**Project tracking
+***Watch QA assigned Features - [http://bit.ly/lWsrWo Spreadhsheet]
+***Assigned new features
+***Reviewed commented bugs
+**Questions
+***Could we reduce the overhead for each release by not creating another wiki page for Manual Testing and just filling the results in the main page? (Now we are filling the results both in the main page and the special created page)
+***From where exactly are the test-runs being cloned since we've seen some testcases that we had modified return to their original broken state in the latest test-runs?
+***Could we set some keywords for each feature so that we can more easily create Bugzilla queries for features - it would make bug tracking a lot easier.
+***We don't have access yet to a place where we can add replacements for the dead items from Litmus
+***Are the queries from the Etherpad's 'Bugzilla queries' section of any help at all?
 == Automation Updates ==
@@ Line 23: / Line 46: @@
 ; WebQA (Selenium)
 * Waverly (Teodosia, Florin)
-* Mozilla
+**Implementing tests for AMO
+**Code reviewing and merging the pull requests
+**Using the [https://www.pivotaltracker.com/projects/310523 AMO Pivotal] to follow the tasks
+* Mozilla (Marlena, Matt)
 ; Desktop (Mozmill)
@@ Line 42: / Line 68: @@
 <i> (eg. Status, top issues) </i>
 * Mozilla (test lead)
+** Firefox 6 beta 3 may be built today
 * Waverley (Ioana, Anna, Andreea, Nicolae)
 ** '''Weekly Status:'''
@@ Line 57: / Line 84: @@
 **'''Questions / Issues:'''
 *** The work week is ongoing. Do we have some special tasks? We saw the section about us in [http://mozqa.sync.in/bt-work-week-july-2011 etherpad] and we would like to know if you need us to participate with something.
-*** Is there a status for the tablet build? There are some differences between tablet and mobile and it will be a great help to see what's been done till now and which are the perspective for tablet version.
+*** Do you have any status regarding the Builds that will be available for the Tablets? We are asking this because there are differences between tablets and mobiles. It would be great for us to know the progress done so far and what else is planned for tablets since we have already started working on this.
 == Take Aways This Week ==
 <i> (eg. Action items) </i>
+* Workweek automation next week - Automation
+** Meeting to has out objectives.
+* Visit to Romania the week after.
+* Answers to '''desktop questions''':
+** Yes, you can reduce the overhead in wiki work by not using separate wikis for manual results. The important thing is to keep notes of major issues found, if any.
+** We'll look into issues when cloning testruns because some updated tests don't make the migration and they end up being broken as they are cloned. - juanb to look into it
+** Yes, you can set your own keywords (in the Whiteboard field) so you can keep track of features for bug queries.
+** Waverley still has no access to a repository to create and link artifacts to it. - juanb to send out forms to be filled out for HG access.
+** The bug queries in the Etherpad are useful to glance at the types of issues found, which have been many. Unfortunately, I've noticed that the bugs don't get traction because their severity doesn't make it obvious that they should be top priority in most cases, but I have no answers to the latter point for now. - juanb
+* Answers to '''Fennec questions''':
+** There are no special tasks that need to be addressed while the workweek is ongoing. Participation in the Etherpad by the Waverley team is not required at the moment. - Kevin
+** For now there isn't an update on the builds that will be available for tablets, and for now use the same Litmus test runs for it as for mobile. - Kevin