Quality/Plans/Handset UX ramp-up 1.1

From MeeGo wiki

(Difference between revisions)

Revision as of 05:13, 6 October 2010

Testability of Features
- Note! Pre-condition is that Testability selection is implemented to Featurezilla - OK
- QA owners to set Feature testability status to Bugzilla and identify final gap - OK
- List of NOK items pointed to Product Management - OK
- Only open area is Photo viewer, that needs improvements.

@@ Line 5: / Line 5: @@
 ** Sanity Testing - OK
 ** Basic Feature Testing - OK
-** Extended Feature Testing - 25th September
+** Extended Feature Testing - 15th October (Done already for Aava)
-** System Functional Testing - 8th October
+** System Functional Testing - 15th October
-** System Non-Functional Testing (Response Time) - 8th October
+** System Non-Functional Testing (Response Time) - 15th October
 * Test Asset Storage (in TestLink)
 ** Sanity Test Set - OK
 ** Basic Feature Testing - OK
-** Extended Feature Testing - ONGOING, 19th September.
+** Extended Feature Testing - OK
 ** System Functional Testing - ONGOING, 19th September
-** System Non-Functional Testing (Response Time) - 24th September
+** System Non-Functional Testing (Response Time) - 7th October
 * Component Test Plans
-** Component Test Plans available - ONGOING, 17th September.
+** Component Test Plans available - OK
 * Testability of Features
@@ Line 26: / Line 26: @@
 * Main Risks / Issues
-** Visibility to Features that are moved from MeeGo 1.1 release to MeeGo 1.2 release. MeeGo 1.1 HandSet UX test sets must be 'cleaned' based on this visibility.
+** Automation solution needed to freed capacity
-** No public N900 weekly SW image, might be that QA must use internal releases for N900