Confirmed users
3,816
edits
QA/TDAI/Goals/2009-Q2: Difference between revisions
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
This is both the agenda and the goals landing page for the Test Development and Automation team for Q2 2009. This is not official yet. It is in draft form. | This is both the agenda and the goals landing page for the Test Development and Automation team for Q2 2009. This is not official yet. It is in draft form. | ||
= High Level Goals = | |||
* Complete build integration work for JS Ref Test, Mozmill, Maemo | |||
* 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. | |||
* Document the testing priorities for new 1.9.2 features. | |||
* 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. | |||
* Code and release Mozmill 1.2, addressing issues that block some segments of testing such as A11y and restartability | |||
** Support the QAE team by writing Mozmill Helper Classes as needed to make test writing easier.(Full set of bugs on this unknown, expect to write between 3 and 7 helper classes over the quarter). | |||
** Tailor the JS Learning Project for Mozmill test writing in order to better enable QAE to write Mozmill tests. | |||
* 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. | |||
** Complete Litmus user flow document for the test management side of Litmus. | |||
= Test Automation = | = Test Automation = | ||
'''Focus:''' Improve the test automation system at harness level. | '''Focus:''' Improve the test automation system at harness level. | ||
'''Goal:''' Increase visibility and expand automation by completing the | '''Goal:''' Increase visibility and expand automation by completing the build integration work for JS Ref Test, Mozmill, and Maemo automation harnesses. | ||
''' Tactics:''' | ''' Tactics:''' | ||
* Institute a measuring system for tinderbox realibility | * Institute a measuring system for tinderbox realibility | ||
* Debug the known, observed, random failures, create a plan for handling random failures going forward. | * Debug the known, observed, random failures, create a plan for handling random failures going forward. | ||
* JS Ref test framework | * Land JS Ref test framework {{bug|469718}} | ||
* Enable Build/Test infrastructure to run Mozmill tests (unit tests at least) | * Enable Build/Test infrastructure to run Mozmill tests (unit tests at least) | ||
** Have Mozmill tests running automatically, reporting to results server and/or staging tboxes (as appropriate) | ** Have Mozmill tests running automatically, reporting to results server and/or staging tboxes (as appropriate) | ||
| Line 26: | Line 37: | ||
'''Goals:''' | '''Goals:''' | ||
* Expand our test coverage by recruiting developers to write targeted tests in critical areas and by devoting | * 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. | ||
* | * Document the testing priorities for new 1.9.2 features. | ||
'''Tactics:''' | '''Tactics:''' | ||
| Line 42: | Line 53: | ||
Goal 2: | Goal 2: | ||
* Be involved in planning discussions for our areas of focus | * Be involved in planning discussions for our areas of focus | ||
* Draft test priority documents, get developer review of those | * Draft test priority documents, get at least informal developer review of those | ||
= 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. | '''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:''' | '''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:''' | '''Tactics:''' | ||
* | * Use our 'hot-spot' list mentioned above as a resource of areas to work from when developing new tests | ||
* Other avenues might 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. | * 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 = | ||
| Line 59: | Line 70: | ||
* 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. | * 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. | ||
* Code and release Mozmill 1.2, addressing issues that block some segments of testing such as A11y and restartability | * Code and release Mozmill 1.2, addressing issues that block some segments of testing such as A11y and restartability | ||
** Support the QAE team by writing Mozmill Helper Classes as needed to make test writing easier. | ** Support the QAE team by writing Mozmill Helper Classes as needed to make test writing easier.(Full set of bugs on this unknown, expect to write between 3 and 7 helper classes over the quarter). | ||
** Tailor the JS Learning Project for Mozmill test writing in order to better enable QAE to write Mozmill tests. | |||
* 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. | * 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. | ||
** Complete Litmus user flow document for the test management side of Litmus. | |||
= Personal Goals = | = Personal Goals = | ||