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 - DONE (2 workers up)
- Reporting to QA-reports - Ville Ilvonen/Esa-Pekka Miettinen - DONE
- Minimize automatic installation time to 10mins - Timo Makimattila, DONE
- OTS worker for UX tests - NOTSTARTED
- Power consumption measurements - NOTSTARTED
Test automation images
- Setup hourly image building for autotest image on own setup (maybe later with BOSS)
- DONE - PC with F13 set up for image creation (rikhalon)
- 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
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.
- looking into rich-core use in MeeGo (sampos)
- 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
- Handset UX weekly testing schedule
| Day | Test set (status) | Release
|
| Monday
| Key feature (OK)
| Preview
|
| Monday
| Acceptance (OK)
| Testing trunk
|
| Tuesday
| Acceptance (Ok)
| Testing trunk
|
| Tuesday
| Sanity (Ok)
| Daily trunk
|
| Tuesday
| DE Dataflow (Ok)
| Preview
|
| Tuesday
| DE use cases (Ok)
| Preview
|
| Wednesday
| Acceptance (Ok)
| Testing trunk
|
| Wednesday
| Key feature (Ok)
| Weekly
|
| Thursday
| DE Dataflow (Ok)
| Weekly
|
| Thursday
| DE use cases (Ok)
| Weekly
|
| Thursday
| Acceptance (Ok)
| Testing trunk
|
| Thursday
| Sanity Ok
| Daily trunk
|
| Thursday
| DE Reliability (Ongoing)
| Weekly
|
| Thursday
| DE Performance (Ongoing)
| Weekly
|
| Friday
| Acceptance (Ok)
| Testing trunk
|
| Friday
| Sanity (Ok)
| Daily trunk
|
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 tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/