Revision as of 06:28, 1 April 2011

QA TODOs (in priority order)

MeeGo.com IRC meetings

There are no special QA meeting, other DE team meetings can be found from here:

• MeeGo-Meeting IRC Schedule

OTS setup and automated hourly testing

OTS setup

• OTS server - Ville Ilvonen/Riku Halonen, DONE
• OTS worker(s) for core tests- Ville Ilvonen/Riku Halonen/Timo Harkonen - DONE
• Reporting of hourly tests to QA-reports - Ville Ilvonen/Esa-Pekka Miettinen/Timo Harkonen - DONE
• Minimize automatic installation time to 10mins - Timo Makimattila, ONGOING
• OTS worker for UX tests - NOTSTARTED
• Power consumption measurements - NOTSTARTED

Test automation images

• Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)

• We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)

If you need something else from QA please tell it to us :)

Applications for testing

• qt-demos already available from the repos
• Small applications that use Qt mobility APIs to access things like sensors to help manual testing

Test asset

• List of open bugs for MCTS
  • see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests

1. WLAN cases
2. Call/SMS cases
3. Audio policy framework cases (lower priority)
4. Camera cases (lower priority)
5. Sensor data cases (Qt Mobility, lower priority)

Crashdb support for ARM core dumps

Core dump processing and backtraces from crashing ARM processes.

• Rich Core dumping
  • Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
    • Changes in MeeGo Gitorious (meego-n900de branch).
    • Dumps are generated in /home/meego/core-dumps
    • In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
    • Get latest packages here
    • Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
  • Fix core-reducer (Something goes wrong, when reducer processes coredump.) - NOT STARTED
  • Oopslog (and lifelog) functionality - NOT STARTED

• Back-end server
  • Set up back-end server for core processing - ONGOING (rikhalon)

Boot time measurement

• Measure and optimize N900 boot time (timakima, ONGOING)

CPU load measurement during audio/video playback

Test Execution Schedule

• Core (Teivas)
• Handset UX weekly testing schedule (Rajala)

QA Tasks For Developer Edition

There is a wiki article about the Developer Edition.

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. There are currently 2 test sets for the Developer Edition, these are the Sanity Test Set and the Feature Test Set. They are described below.

Sanity Test Set

The sanity set should be run automatically on every image. As such it must meet the following requirements:

• 100% automated
• Testing only basic features

Feature Test Set

The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time and a CPU benchmark but this will be expanded later.

Suggestions are welcome.

QA Organization

Error Management

• Error Manager Iekku Huttunen

Usefull links

• Flashing instructions

Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/