Revision as of 08:10, 17 March 2011

QA TODOs

1. OTS setup

• OTS server
• OTS worker(s) for core tests
• OTS worker for UX tests
• Power consumption measurements
• Reporting to QA-reports
• Minimize automatic installation time

2. Applications for testing

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

3. 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)

4. Test Execution Schedule

• Core

• Handset UX weekly testing schedule

5. Test automation images

• Setup image building? own setup or BOSS?
• We need to be able to control included test packages - If images are build by release engineering we need meta test packages to control the content

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

Crashdb support for ARM core dumps

Core dump processing and backtraces from crashing ARM processes.

6. 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.