Confirmed users
3,816
edits
QA/TDAI/Goals/2009-Q2: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
* {{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'' | * {{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) | * {{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 | * {{done|}}Integrate Maemkit with Tinderbox, hand off to build | ||
| Line 43: | Line 43: | ||
* {{done|}}Be involved in planning discussions for our areas of focus | * {{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 | * {{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'' | ** - ''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?) | * {{done|}}Aid Mobile team as needed with their performance testing (seems like Taras is doing much of the heavy lifting?) | ||
* {{ | * {{miss|}}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 missed 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 | * {{done|}}Gather requirements and gather platform performance metrics surrounding network performance for 3.5 | ||
| Line 55: | Line 55: | ||
*** {{done|}}Prioritize recently fixed security bugs for inclusion on the hot-spot list | *** {{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 | ** {{done|}}Create the 'hot-spot' list for each area - JS, Content, Layout/Gfx, Mobile/Ffx Frontend | ||
** {{ | ** {{miss|}}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 | ** 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 | ||