QA/TDAI/WorkWeek Planning

HTML 5 Test Suite

• we have tests
• we have mochitest framework (created by dev for parser error)
  • can leverage that for more testing
• c++ & java DOM comparison testing (needed) make use of dev tool for that
• tokenizer, serializer, test development
• real-world site compare (mikeal)

By August 14

• c++ & java DOM comparison done
• tokenizer, serializer

By Sept 11

real-world site compare (working with mikeal)

Gfx Hardware Acceleration

By August 14

• harness around reftest ext
• get resutls, might need to get a program together that will grab all the information for inclusion when we send the data back up to the results server
• first pass canvas 2d

By Sept 11

• more canvas 2d
• canvas 3d (bundle canvas 3d ext with it)

Multi Process

By August 14

• have a build, keep an eye on the project

By Sept 11

• understand how to get crash reporting data
• begin understanding how to help test this, xpcshell multiprocess, etc
• how do we have to retrofit the crashtest so that it wills still detect crashes.
• see about qae tools (if they will be needed, what will be needed etc)

JS Reftests

By August 14

• Shell test completed
• Browser test completed - patch under review

By Sept 11

• Integrated with buildbot - all they need is the python line and they can integrate it into the buildbot slaves uch that they can integrate it into the parallel setup. (in other words, the build team will own this)
• This will be run on 1.9.1 and m-c

Fennec Test Results

• Discuss data format for results

By August 14

• Scripts running and uploading to server
  • corner cases/fx & build to get buy in on log parsing
• Version 1 of Web site to view the results will be ready
• Aki ready to plug them into his buildbot slaves

By Sept 11

• Addressing Feedback, better views possibly

Mobile TUnit Integration

By August 14

• Patches for test harnesses on WinMo for Reftest and Mochitest
• Manual testing as required
• Settle on the requirements for beta and release builds

By Sept 11

• Maemo Testing (with qae as well) for 1.0 release
• Hopefully run end to end, results posted (but depends on kernel progress)

Automatic Crash Repro

By August 14

• Currently need help getting the crash URLs minimized/tested/bugged (weekly, ongoing)
  • folks will need builds, !exploitable, crashwrangler, lithium
  • can we get security folks to help us with it?
  • most important thing is to get the bug filed with a version of the saved page and then invite folks to minimize
  • Bob will email the crash URLs that are repro'd

• work out the procedure for dealing the URL duplicates
• web app interface for jobs
• pool mgmt on web app
• adding the proper interfaces to sisyphus for communication with the web app

By Sept 11

• prioritize and implement the items from "phase 2" (see wiki), probably not all of them, but the highest priority ones first.
• clean up web app

Test Case Mgr

By August 14

• Test case repository
  • First version of repo to store and retrieve testcases
  • Data model for the test cases
  • web interface for running them (maybe)
  • internationalization for test cases

By Sept 11

• • simple test case writer UI

XBL 2

By August 14

• Plan in place for changes to frameworks
• Plan for sample tests for development review
• Plan to address emulation mode (if one is implemented)

By Sept 11

• Begin Implementing Plan (share into Q4)

Compositor

• In patches, not reviewed, passing existing tests
• May not need any framework help

By August 14

• plugin tests
• iframes
• scrolling tests

QAC

• Bugzilla tab is done
• design lunch next week
• Litmus tab this week
• Aaron's patch for login stuff
• end of the July --> DONE

By August 14

n/a

By Sept 11

n/a

Mozmill Integration

• Meeting tomorrow with catlee and team for 1:30pm