2,088
edits
m (→Manual Testing) |
m (→Manual Testing) |
||
| Line 31: | Line 31: | ||
* Actions - Basic functional testing | * Actions - Basic functional testing | ||
** Setup project/branch in | ** Setup project/branch in Litmus (QA Litmus Admin) | ||
** Crash capture and reporting | ** Crash capture and reporting | ||
** Later nightly builds | ** Later nightly builds | ||
** Supported plug-ins and support for changing plug-ins | ** Supported plug-ins and support for changing plug-ins | ||
*Actions - extended update/download/l10n etc testing | * Furthure Actions - extended update/download/l10n etc testing | ||
** mar updates | ** mar updates | ||
** data migreation | |||
** locales | ** locales | ||
** Weave sync | |||
Consider L10n requirements | Consider L10n requirements | ||
Notes (aakash/timr 11/4/09): | |||
* Basic docs to update profiles | |||
* Docs to do actual testing | |||
* How to install builds | |||
* How to run builds | |||
* Final test for early builds: have build team start and run | |||
** first few builds or for early major tool chain changes: RelEng should install and fire-up new builds rather then have QA find DOA builds. Once there are a few god builds in a row, then we can assume the build process is good and not have RelEng manual test builds. Then the next ste is at add the automated RelEng sanity tests. | |||
* Need release driver - need coordination between groups and keeping good communication and status | |||
edits