Revision as of 07:46, 29 March 2011 (view source) Timoph (Talk | contribs) (→Applications for testing) ← Older edit		Revision as of 10:39, 29 March 2011 (view source) Vilvo (Talk | contribs) (→Test asset) Newer edit →
Line 23:		Line 23:
	== Test asset ==		== Test asset ==
-	* Define what the asset includes	+	* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts  List of open bugs for MCTS]
-	* Automating as many core/ux tests as possible	+	** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
-	* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)	+	# WLAN cases
-	* WLAN cases	+	# Call/SMS cases
-	* Audio policy framework cases (lower priority)	+	# Audio policy framework cases (lower priority)
-	* Camera cases (lower priority)	+	# Camera cases (lower priority)
-	* Sensor data cases (Qt Mobility, lower priority)	+	# Sensor data cases (Qt Mobility, lower priority)
	== Crashdb support for ARM core dumps ==		== Crashdb support for ARM core dumps ==

---

Revision as of 10:39, 29 March 2011

Contents 1 QA TODOs (in priority order) 1.1 OTS setup and automated hourly testing 1.1.1 OTS setup 1.1.2 Test automation images 1.2 Applications for testing 1.3 Test asset 1.4 Crashdb support for ARM core dumps 1.5 Boot time measurement 1.6 CPU load measurement during audio/video playback 1.7 Test Execution Schedule 1.8 QA Tasks For Developer Edition 1.8.1 Sanity Test Set 1.8.2 Feature Test Set 1.9 Error Management 1.10 Usefull links

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
• 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.
  • looking into rich-core use in MeeGo - ONGOING (sampos, rikhalon)
  • 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

• 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 instructions

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