Auto-tools/Meetings/2012-06-25: Difference between revisions

 
(9 intermediate revisions by 4 users not shown)
Line 3: Line 3:
Below are our [https://wiki.mozilla.org/Auto-tools/Goals/2012Q2 top level goals].  Beneath each goal, note any progress made towards that goal this week.
Below are our [https://wiki.mozilla.org/Auto-tools/Goals/2012Q2 top level goals].  Beneath each goal, note any progress made towards that goal this week.


* {{ok|Extend Mobile Platform Automation for B2G and Fennec Native to extend our automation systems to work with specific phone hardware and new development boards for both products.}}
* {{done|Extend Mobile Platform Automation for B2G and Fennec Native to extend our automation systems to work with specific phone hardware and new development boards for both products.}}
** [ahal] Got reftests running on B2G emulator. Still very prototype-y but they mostly seem to pass. Still have a fair amount of work before a patch is ready.
** [ahal] Got reftests running on B2G emulator. Still very prototype-y but they mostly seem to pass. Still have a fair amount of work before a patch is ready.
** [jgriffin] Got B2G builds working for otoro devices.
** [jgriffin] Got B2G builds working for otoro devices.
** [dburns+mdas] Various marionette bug fixes
** [dburns+mdas] Various marionette bug fixes


* {{ok|Datazilla: Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}}
* {{done|Datazilla: Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}}
** [carljm] made administration easier by hooking standalone scripts into Django management commands
** [carljm] made administration easier by hooking standalone scripts into Django management commands
** [jeads] made progress on the security review scheduled on Friday. Has list of action items to complete by then
** [jeads] made progress on the security review scheduled on Friday. Has list of action items to complete by then
** [jeads] Validated the t-test method with the metrics team. Used actual datazilla data.
** [jeads] Validated the t-test method with the metrics team. Used actual datazilla data.
** [jhammel] Got (getting?) jetperf results posted to datazilla
** [jhammel] Getting jetperf results posted to datazilla


* {{miss|Datazilla: Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}}
* {{done|Datazilla: Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}}
** ''NOTE:'' Revised deliverable in light of developer feedback and changed course mid-quarter to deliver a system that would turn TBPL orange/green based on per-patch regression detection, this means we won't deliver the UI by end of quarter, but we'll still land datazilla on production hardware in end of Q2/early Q3 (waiting on hardware to arrive)


* {{ok|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}}
* {{done|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}}
** [jhammel] Refactored and landed the results/reporting in talos. Will make future work easier (see https://bugzilla.mozilla.org/show_bug.cgi?id=755527 for more details)
** [jhammel] Refactored and landed the results/reporting in talos. Will make future work easier (see https://bugzilla.mozilla.org/show_bug.cgi?id=755527 for more details)


* {{ok|Refactor how rapid-release tracking flags are implemented for improved performance and maintainability}}
* {{done|Refactor how rapid-release tracking flags are implemented for improved performance and maintainability}}
** Code complete, just needs testing (and lots of it).
** May schedule for after 4.2 so that we don't have to retest with 4.2.


* {{risk|Upgrade bugzilla.mozilla.org to Bugzilla version 4.2}}
* {{risk|Upgrade bugzilla.mozilla.org to Bugzilla version 4.2}}
** [glob+dkl] Testing of BMO 4.2 code and debugging and fixing of several issues such as HTML email, SecureMail, etc.
** [glob+dkl] Testing of BMO 4.2 code and debugging and fixing of several issues such as HTML email, SecureMail, etc.
** [glob] Successful QA Contact Migration test run on bugzilla-stage.mozilla.org. Scheduled for around July 4th to 6th.  
** SecureMail raising more issues than expected. Still need to determine what testing needs to be done before sanitizing staging server db.
** Hopefully aiming for release around July 23.


* {{ok|Reduce android test automation instability and make it easier for the web QA and desktop QA teams to write and run automated tests.}}
* {{done|Reduce android test automation instability and make it easier for the web QA and desktop QA teams to write and run automated tests.}}
** [whimboo] Fixed several mozmill bugs, improved mozmill's logging module ({{bug|749104}}) and did some python refactoring for mozmill/jsbridge
** [davehunt] Released pytest-mozwebqa (http://blargon7.com/2012/06/announcing-pytest-mozwebqa-1-0/)
** ''NOTE:'' We did great with this, so great that we turned on 250,000 more tests and made everything more unstable again. The big shift here though is that we went from running "only what will pass" on mobile to running "everything except the known failures" and we have developers working on the failures. ''This is a huge step forward for mobile, given the Fennec Project's historic love/hate relationship with automated tests.''


== Highlights ==
== Highlights ==
Line 34: Line 41:


== In-Depth Project Discussion ==
== In-Depth Project Discussion ==
[[Auto-tools/Projects/Marionette|Marionette]], presented by mdas
== The Overview ==


''Progress, notes, problems, and other statuses about current projects. Add any new projects to this template!''
''Progress, notes, problems, and other statuses about current projects. Add any new projects to this template!''
Line 127: Line 138:
=== [[Auto-tools/Projects/WarOnOrange|War on Orange]] ===
=== [[Auto-tools/Projects/WarOnOrange|War on Orange]] ===
* [edmorley] Re-disabled on Android a few tests switched on by {{bug|761125}}, the rest of the 200,000+ tests seem to be holding up however \o/
* [edmorley] Re-disabled on Android a few tests switched on by {{bug|761125}}, the rest of the 200,000+ tests seem to be holding up however \o/
* [mcote] Nearly done Orange Seed. Back end complete and front end progressing.


=== Web QA ===
=== Web QA ===
Line 140: Line 152:


* [carljm] wrote a tool for project management to pull down basecamp/gaia bugs from bugzilla and github and combine into a single CSV file
* [carljm] wrote a tool for project management to pull down basecamp/gaia bugs from bugzilla and github and combine into a single CSV file
== The Overview ==
''Put project-specific status reports here''


== Upcoming Events ==  
== Upcoming Events ==  
Confirmed users
1,927

edits