Schedule

• Tuesday 23rd
  • Travel Day
• Wednesday 24th
  • 10:00 - [Futurama Presentation]: Plans and ideas for the future of Mozilla automation
  • 11:00 - Future of Mozbase, what is left to do, who uses it, development processes, merging to m-c, talos, etc.
  • 13:15 - [Mobile Testing Meeting]
  • 15:00 - Mozbase versioning (proposed, jhammel)
  • 16:00 - [Mozharness Meeting]
• Thurdsay 25th
  • 11:00 - Discussion on reporting stuff: mozlog, moztest
  • 13:00 - [B2G automation meeting]
  • 14:00 - [Signal From Noise]
  • 15:00 -
• Friday 26th
  • Community hack day
  • 11:00 - Public meeting on Futurama: come one, come all, and give us your ideas!
  • 14:00 - Trial run for Mobile Test Summit talks (marionette and eideticker)
  • 18:30 - [Team wide dinner]
• Saturday 27th
  • Community hack day
  • We should find an activity to do
• Sunday 28th
  • Travel Day

Community Hack Day

This is an opportunity for us to stop working on the same things that we do all day and focus on delivering something as a team. Please add projects which are actionable and doable in a 2 day scope.

Mozbase on Mozilla Central

dust off old patches and get mozbase virtualenv running on cedar for unittests

• bug 746546 - add info to mozinfo [needs info!]
• bug 746244 - port profileserver to mozbase
• bug 746243 - port mochitest to mozbase

Mochitest Validator

Analyze unittests for common failures.

There is an existing tool which is used to verify webapps (HTML/JS/CSS files). Maybe we can use some of the logic here and tailor it to detect patterns that cause random oranges.

https://github.com/mozilla/app-validator

Datazilla analyzer

Write a tool which will query the new fancy datazilla API and provide pass/fail results to developers.

• update compare.py to query datazilla API and verify after calculating the data we get identical numbers as the graph server
  • bonus points for optionally showing the more detailed data per page
• create a web page which uses the datazilla api to show the auxillary data in a graph.
  • start with [windows 7 tp5n] xperf data and show the 9 values progressing over time
• Make a landing page for datazilla. This one is clearly not cutting it https://datazilla.mozilla.org. The web services available to do this are documented here http://datazilla.readthedocs.org/en/latest/webservice/#reference-data.
  • This page should display all of the datazilla projects (talos, stoneridge, b2g, jetperf, test) in a side bar.
  • Allow the user to select a project and then display a summary in the main display area of the browser. Here are some example web service endpoints to use:
  • https://datazilla.mozilla.org/talos/refdata/perftest/runs_by_branch?days_ago=30
  • https://datazilla.mozilla.org/talos/refdata/objectstore/db_size
  • https://datazilla.mozilla.org/talos/refdata/perftest/ref_data/options
  • https://datazilla.mozilla.org/talos/refdata/perftest/ref_data/tests
  • https://datazilla.mozilla.org/talos/refdata/perftest/ref_data/pages
  • https://datazilla.mozilla.org/talos/refdata/perftest/db_size
  • https://datazilla.mozilla.org/talos/refdata/objectstore/error_count?days_ago=30
  • https://datazilla.mozilla.org/talos/refdata/objectstore/error_list?days_ago=30

Documentation Sprint: Automation frameworks

A new effort has been started to make MDN the primary documentation for our automation tools and frameworks (Mochitest, Reftest). The idea is to create a basic landing page for each of our projects. A template has been created, and the first framework has been covered. Let's see if we can make more progress during a hack session! The work is being done in this github repository.

Documentation Sprint: Documenting Mozbase

Comprehensive documentation across mozbase modules would be highly desirable. It looks like sphinx would be a good solution for this task (see wlach's post to mozilla.tools)

This hackfest would focus on both adding documentation pages for individual mozbase modules (mozprocess, mozrunner, etc.) as well as making sure that the function/class docstrings we're using generate good documentation. Work will be done in the main mozbase repository, more details to come.

MoCo logistics

If you're a MoCo employee, you can see our internal planning page here:

https://intranet.mozilla.org/Auto-tools/Toronto_Ateam_Meetup_October_2012

(if you're not a MoCo employee, don't feel left out, there's nothing interesting there)