QA/Browser Technologies/Meetings/2013-01-08: Difference between revisions

QA/Browser Technologies/Meetings/2013-01-08 (view source)

Revision as of 15:07, 8 January 2013

431 bytes removed , 8 January 2013

→‎Fennec Updates

Andreea.pod

1,148

edits

@@ Line 10: / Line 10: @@
 * SoftVision (Ioana, Andreea, Catalin, Adrian, Nicolae, Paul)
-'''Work done since last meeting'''
+*'''Work done since last meeting'''
-** [http://goo.gl/DTc28 Logged issues]
+** [http://goo.gl/vsRDB Logged issues]
 ** Watch assigned features - [https://docs.google.com/spreadsheet/ccc?key=0AhE7m4JB2j6tdGVKQlRHUnFWVEZXNFFJbHo0RVpQMmc#gid=0 spreadsheet]
 ** Qa-wanted bugs
 ** Regression window wanted
 ** Bug verification
-** Firefox Mobile 18 Beta 3. Results [https://wiki.mozilla.org/QA/Fennec/18/Beta/3 here]
+** Firefox Mobile 18 Beta 5. Results [https://wiki.mozilla.org/QA/Fennec/18/Beta/5 here]
+** Firefox Mobile 18 Beta 6. Results [https://wiki.mozilla.org/QA/Fennec/18/Beta/6 here]
+** Firefox Mobile 18 Beta 7. Results [https://wiki.mozilla.org/QA/Fennec/18/Beta/7 here]
+** Firefox Mobile 18 RC 1. Results [https://wiki.mozilla.org/QA/Fennec/18/RC/1 here]
 ** In-moztrap B2G - create test cases from use cases
 * '''Automation testing status'''
 ** Progress on [https://docs.google.com/spreadsheet/ccc?key=0Ak8KPfUd1-5udC1FRXBHMlA2MkJLOEp0NFkxTnBtS1E#gid=0 Smoke test Automation]
@@ Line 34: / Line 38: @@
 *'''Important bugs:'''
 **{{Bug|819327}} - crash in ext.odex
-**{{Bug|818874}} - URL Bar is covered on the right edge by the Tabs Menu button
-**{{Bug|818494}} - Swipe to close tab action is sensitive
 **{{Bug|818814}} - The mobile version of nfl.com has layout issues on Firefox Mobile
+**{{Bug|821227}} - Top Sites list is replaced by the search engine results when the hardware keyboard is closed
-*'''Issues/Questions/ Proposals'''
+**{{Bug|821672}} - External links are not loaded if Fennec is already opened
-** The ramp-up process on automation is almost complete for Paul and Nicolae. Also we are almost done creating tests for the Smoketest suite. How should we proceed in choosing the new tests to automate? Should we each take an old feature from the BFTs and automate as much as possible from it or should we concentrate on the newest features added?
-** 12/21 Final decision for Firefox 18 Beta testday?
-'''Automation testing status'''
-* Progress on [https://docs.google.com/spreadsheet/ccc?key=0Ak8KPfUd1-5udC1FRXBHMlA2MkJLOEp0NFkxTnBtS1E#gid=0 Smoke test Automation]
-* Bugs with work in progress:
-* Bugs awaiting review:
-* Bugs with accepted patches:
-'''Important bugs:'''
-'''Issues/Questions/ Proposals'''
 == BrowserID Updates ==