Auto-tools/Projects/2011Q2

From MozillaWiki
Jump to: navigation, search

Below are our raw notes. I'm trying to clean these up into something useful.

Here is one useful way to view the dependencies we have: https://wiki.mozilla.org/User:Ctalbert/Testme

From that, I'm moving toward a table format because it is easier to follow at a glance. Please edit this table with details for your projects:

2011Q2 Projects Table

It is my intention this table will replace the one on our main projects page.

Talos

  • Addons Perf Testing tool (anode) P1
    • 7 machines as on-demand testing tool (beta)
  • Tp5 completed actual useful content that people browse in screen going to have a public tp set (anode) P1
  • User Responsiveness (ted, platform, anode/jmaher?) P1
    • what events to measure
    • how to get the numbers back up into talos
    • native events?
    • need mechanism to annotate where the event took place in the outputted log
  • Fix Talos Desktop for E10S support (small bug, jmaher)
  • other talos bugs from the addon authors
  • [perf team requests] from taras,sdwilsh (jmaher, anode?) P2?
    • finish xperf (upload .etl, parse etl and upload csv to log file for disk IO, etc...)
    • use xperf to measure cpu, disk, memory of overall system, not cmanager_win32.py
    • stop measuring tests by time, measure by other metrics (disk io, page faults, etc...)
    • change pageloader to use native events or sendKeyEvent to enter new URL's (i.e. use the awesomebar)
    • change pageloader to optionally click a link (via js+dom) and open in a new tab

= Mozmill = (P2?)

  • finish + release mozmill 2.0 (harth, jhammel, ctalbert(half time))
  • put mozmill *back* into buildbot and TBPL (some cleanup there as well) jhammel
  • fix mozmill-automation, comm-central's automation (optionally), and ideally start outreach to other mozmill consumers (not priority)
  • e10s support - investigate

= Crossweave2 = (aka TPS) jgriffin, services, about a month) (P1)

= F1 = (jgriffin, bmoss to handle) (P?)

  • Too many unknowns

= Autolog = (jgriffin, mcote, jmaher) 1month or so (P1)

  • complete initial implementation
  • integrate with Crossweave2
  • potentially integrate tinderbox data

= ProfileManager ? = (ctalbert/bmoss talk to project managers) (P2)

  • add features per Cheng's requests for support team
  • publicity? documentation?

= manifests = (jmaher, jhammel) (P1-P2)

  • support for mechanism of reftest style manifest
  • finish code and disseminate information and document
  • land xpcshell
  • prototype mochitest?

= autobot: transform and roll out! = (jhammel) (P2)

  • into deployed instance(s)
  • need machines

= toolbox = (waiting on brasstacks, UI), mcote, P1-p2?

  • figure out what needs to be finished up, put somewhere, and announce it (and somehow get people to use it)

infrastructure

  • Vm to replace brasstacks (bmoss will escalate) P0 -- preferably also a staging server
  • bugzilla dashboard? P5
  • Rapid Requirements stuff ????(P1)
    • Features turning on and off through nightly, aurora, beta, etc (could be high P1)

Bugzilla

  • Release 4.0 P1
  • Pulse integration (AMQP) P1
  • Native REST API P1
  • Better integration with other development/qa tools. P2-p3
  • UI improvements (upstream bugzilla tweaks enhancements where relevant) P2

= MozHarness/Buildbot stuff = (ted, jgriffin, ctalbert, jmaher) P3

  • going to span all projects - talos/unittest/etc
  • process, profiles, environment, os directives, args, mozrunner, +more
  • use plugable modules which could also stand alone
  • pilot project with xpcshell

= Speed Tests = (mcote) P1 (nearly done)

  • Win, Mac, Linux boxes running speedtest client
  • Eye-pleasing reports
  • Ability to run locally & get results without server (?)

= Bughunter = (bc, mcote, jgriffin) P2

  • Complete Mysql conversion?
  • Temporarily get a new vm to roll out on (IT)
  • Purify

random projects

  • über crawl - svg, css, js, - metrics guys and the teams that want it (time permitting, i wouldn't mind working on that - jhammel)
  • eideticker - ???

= HTML Record Playback = (work with dev tools) P2

  • when you go to a website and things die
  • record what happens
  • play back the traffic

= Android Support = (ctalbert, bmoss, jmaher) P1

  • Droidfarm support
  • Continuing releng support

= WOO Support = (mcote jgriffin) P1 = test harnesses with servers = (Identity, crossweave, firebug, sync, safebrowsing apps etc)

  • need a way to run these in automation with the test server
  • would like to automatedly run the tests against staging
  • how do we run these tests on a per-checkin test.
  • record/replay playback stuff
Retrieved from "https://wiki.mozilla.org/index.php?title=Auto-tools/Projects/2011Q2&oldid=300748"