Confirmed users
3,816
edits
QA/TDAI/Goals/2009-Q2: Difference between revisions
→Test Development
| Line 46: | Line 46: | ||
** - ''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?) | ||
* {{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 | * {{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 | * {{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 | ||
** {{ | ** {{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 | ** 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 | ||