Revision as of 05:18, 27 May 2011

Meego Developer Edition Quality Assurance

Quality Assurance for Meego Developers Edition. Developer Edition QA uses many same components as in core Meego, therefore remember to look Meego core quality page. Monitoring the Developer Edition maturity is one of the main tasks of Developer Edition QA. The current maturity status can be found from the Status page.

Organization

• Error Management
  • Error Manager: Iekku Huttunen
• QA Tools
• Core Testing
• User Experience Testing (UX)

Reports

• General DE N900 Feature status
• Performance results
• Dataflow reports
• Use case reports

Meetings

QA IRC meeting every Tuesday:

• MeeGo-Meeting IRC Schedule

N900 DE Blocker Bug Triage meeting minutes:

• Meeting minutes 19-05-2011
• Meeting minutes 12-05-2011
• Meeting minutes 05-05-2011
• Meeting minutes 21-04-2011
• Meeting minutes 14-04-2011
• Meeting minutes 07-04-2011
• Meeting minutes 31-03-2011
• Meeting minutes 24-03-2011

QA Tools

Developers Edition uses same QA Tools as in core Meego. For more information please refer to the Quality/QA-tools.

QA-Tools Task List

List of tasks the QA-Tools are doing for Meego Developer Edition. If you need something from QA please tell it to us :)

OTS setup

(Open Testing System)

• OTS server DONE
• OTS worker(s) for core tests- DONE
• Reporting of hourly tests to QA-reports - DONE
• Minimize automatic installation time to 10mins - DONE
• OTS worker for UX tests - NOTSTARTED
• OTS Worker(s) for DE tests - ONGOING (timakima)
• 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)
• Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

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

We are using mainly MCTS test assets, so please refer to the MCTS page. You can find list of open bugs also from there.

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

Crash analysis support for ARM core dumps

Automated testing and crash reporting

Core dump processing and backtraces from crashing ARM processes (click the image on right).

• 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 (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
  • Oopslog (and lifelog) functionality - NOT STARTED

• Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

• Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

• Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

• testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

• Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

• After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
  • testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.

Core Processing Backend

<crashes>
 <crash-id>1234567890ABCDEF</crash-id> 
 <crash-id>1234567890ABCDEF</crash-id>
 <crash-id>1234567890ABCDEF</crash-id>
</crashes>

• The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

• The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

• Upload processed crash data using Crash Reports API - DONE (rikhalon)

Boot time measurement

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

CPU load measurement during audio/video playback

Application Manager

• Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

UX testing

Test execution schedule

• UX testing schedule: DE / Meego.com testing

Performance Testing

Performance testing results done from UI can be found here

Core Testing

QA Tasks For Developer Edition

QA tasks for the Developer Edition differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in Developer Edition Targets. 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.

Test Sets

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, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

Testing schedule

Core QA Team Backlog

The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

Continuous tasks

• Bug verification

Backlog

• Testcase automation list

In progress

• DE Hourly Automation improvement
• Wiki clean/update (waiting for comments)

Done

• * Plan Feature testset (.xml updated)
• Create weekly schedule for MRT (currently in draft form)
• Week 15 DE Sanity Testing
• Maturity statement of Alpha RELEASE (result in QA-report)
• Alpha RELEASE testing

QA Tasks for MeeGo.com N900

Test execution schedule

• MeeGo.com N900 Core weekly test schedule for MeeGo1.3

META team backlog for MeeGo1.2 N900

Continuous tasks

• Bug verification
• MeeGo1.3 N900 daily validation

Backlog

• Optimize acceptance automation script
• Testability for MeeGo1.3 features.

In progress

• Automation testing for trunk:test and trunk image

Done

• Publish automation test result
• MeeGo1.2 feature verification

Usefull links

• Flashing instructions

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