Revision as of 13:25, 21 March 2011

QA TODOs (in priority order)

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 - ONGOING (2 workers up)
• OTS worker for UX tests
• Power consumption measurements
• Reporting to QA-reports
• Minimize automatic installation time to 10mins - Timo Makimattila, DONE

Test automation images

• Setup hourly image building for autotest image on own setup (maybe later with BOSS) - Riku Halonen ONGOING (setting up F13 machine for image creation)
• We need to be able to control included test packages

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

Applications for testing

• Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

Test asset

• Define what the asset includes
• Automating as many core/ux tests as possible
• Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)
• WLAN cases
• Audio policy framework cases (lower priority)
• Camera cases (lower priority)
• Sensor data cases (Qt Mobility, lower priority)

Crashdb support for ARM core dumps

• Core dump processing and backtraces from crashing ARM processes.

Boot time measurement

• Measure and optimize N900 boot time

CPU load measurement during audio/video playback

Test Execution Schedule

• Core

• Handset UX weekly testing schedule

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.

Error Management

• Error Manager Iekku Huttunen

Usefull links

• Flashing instructions http://wiki.meego.com/ARM/N900/Install/MMC

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