Revision as of 13:14, 31 January 2011

Testability Status Progress

Testability Status Progress for Handset UX 1.2 Features

• Status from 31st January 2011
  • Total 263 Features analyzed
  • ~94% of Features are testable
  • ~6% of Features are not testable

• Status from 21st November 2010
  • Total 240 Features
  • ~80% of Features are testable
  • ~20% of Features are not testable

• Status from 25th October 2010
  • Total 217 Features went through
  • 75% of Features are testable
  • 25% of Features are not testable
  • Testability in Featurezilla

• In most of not testable features QA owner has added comment what is missing from feature to get it testable.
• Next Step-1: Go findings through with Product Management to get not testable features to testable.
• Next Step-2: Re-calculate testability 12th November

Testability Status Progress for HandSet UX 1.1 Features

• Status from 13th August:
  • All HandSet UX 1.1 Features went through
  • 52.6% of Features are testable
  • 47.4% of Features are not testable and thus QA is not able to design test cases for those
  • Next step: QA owners will contact to feature owners in case of testability NOK features and provide detailed feedback to them to improve quality of features
  • Timeline for QA owner to give relevant feedback: 20th August 2010

File:HandSet 1.1 UX Feature Testability Review Status Wk32.xlsx

• Status from 3rd September
  • 425 Features went through
  • Testability value set to Features in Featurezilla
  • ~80% of Features are Testable
  • Most risky areas currently are Camera Application, Photo Viewer, Video Player and Web Browser

• Status from 9th September
  • 373 Features still tagged to MeeGo 1.1 release
  • ~90% of Features are Testable
  • Only risky area currently Photo Viewer

• Link to used testability checklist: Quality/TestabilityChecklist