Confirmed users
3,816
edits
QA/TDAI/Goals/2009-Q2: Difference between revisions
→Test Development
No edit summary |
|||
| (36 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
This is both the agenda and the goals landing page for the Test Development and Automation team for Q2 2009. | |||
= High Level Goals = | |||
* Increase visibility and expand automation by completing the build integration work for JS Ref Test, Mozmill, and Maemo automation harnesses. | |||
** ''JS Ref Test is at risk, mozmill is ok, maemo is ok.'' | |||
* {{done|}}Support the 1.9.2 feature and performance work with functional test writing and aid in detailing/specifying new performance metrics (work with Fx Front End and Platform). | |||
** {{done|}} ''We completed work with networking performance, it is unclear if help is needed for front end, and mobile perf work is ongoing.'' | |||
* Expand our test coverage by recruiting developers and community to write targeted tests in critical areas and by devoting one day every other week to publicly work on test development for all available harnesses. | |||
** {{done|}} ''Have not done as good a job at this as we would have liked early in the quarter due to 3.5 slippage, but will make up for it toward the end.'' | |||
* Maintain and improve test tools to better enable people to do both manual and automated testing. | |||
** QAC, Mozmill, and the Results server are the tools we aim to update this quarter. | |||
** {{ok|}} Mozmill is ok. {{risk|}} QAC is at risk. | |||
= Test Automation = | = Test Automation = | ||
''' | '''Focus:''' Improve the test automation system at harness level. | ||
''' | '''Goal:''' Increase visibility and expand automation by completing the build integration work for JS Ref Test, Mozmill, and Maemo automation harnesses. | ||
* | |||
* Enable Build/Test infrastructure to run Mozmill tests (unit tests at least) | ''' Tactics:''' | ||
** Have Mozmill tests running automatically, reporting to results server and/or staging tboxes (as appropriate) | * {{done|}}Institute a measuring system for tinderbox realibility | ||
* Integrate Maemkit with Tinderbox, hand off to build | * {{done|}}Debug the known, observed, random failures, create a plan for handling random failures going forward. | ||
* {{risk|}}Land JS Ref test framework {{bug|469718}} - ''at risk due to 3.5 slip, getting build resources is hard and this feature is coming in late'' | |||
* {{ok|}}Enable Build/Test infrastructure to run Mozmill tests (unit tests at least) | |||
** {{miss|}}Have Mozmill tests running automatically, reporting to results server and/or staging tboxes (as appropriate) | |||
* {{done|}}Integrate Maemkit with Tinderbox, hand off to build | |||
'''Other Harness Level Projects''' | |||
* {{done|}}Research and develop tools to run unittests on Windows Mobile. This includes remote launching and refactoring existing tools | |||
** Prototype in Q2 | |||
** formally finished in Q3 | |||
* {{ok|}}Create a method for writing Fennec specific automated mochitests, xpcshell tests, reftests etc. | |||
= Test Development = | = Test Development = | ||
''' | '''Focus:'''Expand test coverage across all harnesses and in all areas where more test coverage is needed. | ||
* | |||
** | '''Goals:''' | ||
** | * ''Goal 1:'' Support the 1.9.2 feature and performance work with functional test writing and aid in detailing/specifying new performance metrics (work with Fx Front End and Platform). | ||
** Create | * ''Goal 2:'' Expand our test coverage by recruiting developers and community to write targeted tests in critical areas and by devoting one day every other week to publicly work on test development for all available harnesses. | ||
** | |||
'''Tactics:''' | |||
Goal 1: | |||
* {{done|}}Be involved in planning discussions for our areas of focus | |||
* {{ok|}}Draft test priority documents detailing the new features we will concentrate on for functional testing, get at developer review of those | |||
* {{miss|}}Write those functional tests | |||
** - ''3.5 slip has prevented us from concentrating as much here as we had anticipated'' | |||
* {{done|}}Aid Mobile team as needed with their performance testing (seems like Taras is doing much of the heavy lifting?) | |||
* {{drop|}}Gather requirements and create mechanism for Firefox front end team's user performance metrics from "dirty" profiles - ''not sure how much this is still needed, and marking dropped as this item has been pushed into q3 by 3.5'' | |||
* {{done|}}Gather requirements and gather platform performance metrics surrounding network performance for 3.5 | |||
Goal 2: | |||
* {{done|}}Create a list of 'hot-spots' where we need more testing and devote one day every other week to writing test cases each in our specific areas. Determine the 'hot-spots' by analyzing: | |||
*** {{done|}}Query recent in-test-suite-? flags to find areas where people have flagged areas for more test development | |||
*** {{done|}} Use those areas to drill down into relevant files and determine where to concentrate test cases based on areas where we have low/incomplete code coverage | |||
*** {{done|}}Prioritize recently fixed security bugs for inclusion on the hot-spot list | |||
** {{done|}}Create the 'hot-spot' list for each area - JS, Content, Layout/Gfx, Mobile/Ffx Frontend | |||
** {{drop|}}Bring the list to developers to get them to help create tests - ''With the unrelenting focus on code blockers for 3.5 we did not feel it appropriate to bug developers with this'' | |||
** Not having done this before, use a time based approach. Next time we will look at number of test cases written this quarter and see how to change this goal going forward | |||
= Community Leadership = | = Community Leadership = | ||
''' | '''Focus:'''Broaden the Test Development Team's reach and impact by recruiting more people to help and being more public in all we do. | ||
'''Goal:'''Hold test development days where we publicly focus on writing tests on our 'hot-list' for each of our different test harnesses. Invite community and developers to join us. | |||
'''Tactics:''' | |||
* {{ok|}}Use our 'hot-spot' list mentioned above as a resource of areas to work from when developing new tests | |||
* {{ok|}}Other avenues might be established by creating a well defined set of tools/wishlist projects (including detailed, concrete steps we need people to take) that we want help with: Litmus Redesign, Qac, Mozmill Helper Functions, Mozmill Features, Community Reftesting, etc. | |||
= Test Tools = | = Test Tools = | ||
''' | '''Focus:''' Create, maintain, and improve testing tools needed for ourselves and the larger testing community | ||
''' | |||
''' | '''Goal:'''Maintain and improve test tools to better enable people to do both manual and automated testing | ||
'''Tactics:''' | |||
* {{risk|}}Provide a new QAC to the testing community. Focus on fixing usability issues with the tool so that people can more easily use that tool in their testing of Firefox. | |||
* | * {{ok|}}Code and release Mozmill 1.2, addressing issues that block some segments of testing such as A11y and restartability | ||
* | ** {{ok|}}Support the QAE team by writing Mozmill Helper Functions as needed to make test writing easier.(Full set of bugs on this unknown, expect to write between 3 and 7 helper functions over the quarter, some may actually be folded into the main product if appropriate). | ||
* | ** {{done|}}Tailor the JS Learning Project for Mozmill test writing in order to better enable QAE to write Mozmill tests. | ||
* | * {{risk|}}Release first version of new results server which will be the home for Mozmill functional test reporting and future home of Litmus test result reporting and Fennec automation test result reporting. - ''This is on hold waiting on IT resources, blocked by the 650 castro move'' | ||
** {{ok|}}Complete Litmus user flow document for the test management side of Litmus. | |||