QA/Firefox3.5/Places TestPlan: Difference between revisions
< QA | Firefox3.5
Jump to navigation
Jump to search
m (→Test Strategy) |
|||
| Line 18: | Line 18: | ||
= Schedule Scoping = | = Schedule Scoping = | ||
* performance is watched closely by devs on each check-in | |||
* FFT's will be run for beta 1 and Final RC 1 (2 hours per platform each run) | |||
* BFT's will be run for any other point release (1 hour per platform each run) | |||
= References = | = References = | ||
Revision as of 18:06, 30 September 2008
- Places Test Plan
Overview
Ensure feature enhancements and performance improvements work as prescribed without causing any regressions from the current version (3.0.x)
Test Strategy
List major areas of test coverage:
- Places (Bookmarking, History and Library) UI
- Database and query performance
- could be a series of tests that profile common Places queries (see bug 451607)
- Areas not covered: since the performance improvement fixes will be affecting most of Places, we'll be testing everything we can.
- Test cases will be in unit tests and Litmus (with possible conversion of some Litmus cases to Mozmill)
- Existing test cases used for 3.0 as well as new test cases added for new features (see bugs below)
Schedule Scoping
- performance is watched closely by devs on each check-in
- FFT's will be run for beta 1 and Final RC 1 (2 hours per platform each run)
- BFT's will be run for any other point release (1 hour per platform each run)
References
Main tracking bugs:
- tag autocomplete bug 415960 fix in progress
- bulk tagging/editing bug 412002 verified fixed, inlitmus+
- reducing fsyncs and dependencies (bug 442967 fix on try server
- transaction manager perf improvements bug 432706 fix in progress
- bug 450290 – Sync the temp tables to the permanent tables fix in progress