MeeGo wiki - User contributions [en]

Quality/QA tools development

2011-08-09T04:44:00Z

Asinnela: /* Tools and Maintainers */

= QA tools development =

This page provides information on the development activities and practices of QA tools. The focus is on presenting things that are relevant for people interested in developing the tools. The main page for the end users is [[Quality/QA-tools|here]].

Anyone is welcome to contribute and non-member contributions will be treated with same process and review as member contributions. We follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://meego.gitorious.org/meego-quality-assurance/ git repositories] and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.

'''Targets:'''

* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance
* Improve MeeGo test automation (execution and software installation) - target from MeeGo release engineering

"As Core OS release release manager I want to verify trunk:testing packages frequently so that I know the quality of nightly/weekly releases."

== Tools and Maintainers ==

Tool maintainers are selected based on developer experience with particular tool/package or seniority. Tool maintainers have been agreed [[Quality/QA-tools/Meetings|in the QA-tools meeting]] Tuesday September 7th 2010. Changes, if needed, are discussed also there.

In practice only tool maintainers will have commit and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Others must follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines] to submit patches or personal clone + merge request approach.

The maintainer of the tree shall update the changelog.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Gitorious'''||'''Maintainer''' ||'''Substitute'''
|-
| [[Quality/QA-tools/Test-definition|test-definition]]||[http://meego.gitorious.org/meego-quality-assurance/test-definition Gitorious] || Sami Lahtinen || Timo Härkönen
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||[http://meego.gitorious.org/meego-quality-assurance/testrunner-lite Gitorious] || Sami Lahtinen || Kyösti Ranto
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || [http://meego.gitorious.org/meego-quality-assurance/testrunner Gitorious] || Kyösti Ranto || Timo Härkönen
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] ||[http://meego.gitorious.org/meego-quality-assurance/testplanner Gitorious] || Kyösti Ranto || N/A
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] ||[http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing Gitorious] || Timo Härkönen || Timo Mäkimattila
|-
| [[Quality/QA-tools/OTS|OTS - Open Test System]] ||[http://meego.gitorious.org/meego-quality-assurance/ots Gitorious] || Elias Luttinen || Ville Niutanen
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||[http://gitorious.org/qa-tools/meego-ai Gitorious] || Timo Härkönen || N/A
|-
| [[Quality/TestSuite/MCTS|MeeGo Core Test Suite]] || [http://meego.gitorious.org/meego-quality-assurance/mcts/ Gitorious] ||Matti Salmi || Jeff Zheng
|-
| [[Quality/Netbook Test Suite and Utilities|MeeGo Netbook Test Suite]] || [http://gitorious.org/qa-tools/mnts/ Gitorious] ||Jeff Zheng || N/A
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || [http://gitorious.org/qa-tools/qtuitest-mbt-adapter Gitorious] || Riku Halonen || N/A
|-
| [http://min.sourceforge.net/ MIN test framework] || [http://meego.gitorious.org/meego-quality-assurance/min Gitorious] || Joonas Kylänpää || Timo Mäkimattila
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || [http://gitorious.org/TDriver Gitorious] || Petri Kiiskinen || Tatu Lahtela
|-
| Rich Core dumper || [http://meego.gitorious.org/meego-quality-assurance/rich-core Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter settings || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter-settings-public Gitorious] || Carol Rus || Raimo Gratseff
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] || [http://meego.gitorious.org/meego-quality-assurance/hat-control Gitorious] || Marko Junttila || Riku Halonen
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || [http://meego.gitorious.org/meego-quality-assurance/qa-reports Gitorious] || Sami Hangaslammi || Jarno Keskikangas
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || [http://meego.gitorious.com/meego-quality-assurance/scripts-and-utils Gitorious] || N/A || N/A
|-
| [[Quality/TestSuite/handset-test-suite/handset-ux-test_Releases | handset_ux_tests]] || [http://meego.gitorious.com/meego-quality-assurance/handset-ux-tests Gitorious] || JessicaJi || N/A
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] || [http://meego.gitorious.org/meego-quality-assurance/meego-testing-hudson-plugin Gitorious] || Alexey Kuznetsov || Timo Härkönen
|-
| Service OS based Flasher || [http://meego.gitorious.org/meego-quality-assurance/meego-ai-serviceos Gitorious] || Jing Wang || N/A
|-
| Qpid C wrapper library - libcqpid || [http://meego.gitorious.org/meego-quality-assurance/libcqpid Gitorious] || Sami Lahtinen || N/A
|-
| [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || [http://meego.gitorious.org/meego-quality-assurance/auto-ux-testlib Gitorious] || Shao-Feng Tang|| Helia Correia
|-
| [[Testkit_Howto|testkit-lite]] || [http://meego.gitorious.org/meego-quality-assurance/testkit-lite Gitorious] || Jing Wang|| N/A
|-
| [[Testkit_Howto|testkit-manager]] || [http://meego.gitorious.org/meego-quality-assurance/testkit-manager Gitorious] || Shao-Feng Tang|| N/A
|}

If you are interested in the user experience work regarding these tools, you can find more information [[Quality/QA-tools/User experience|here]].

=== Overview ===

The figure below tries to summarize the relations and tasks of the tools when used in test automation context.

[[File:testautomationtools.png]]

xfig file:[[File:qatools.fig]]

== Release Practices ==

Here is the workflow for QA tools release practices.

{| border="1" cellspacing="0"
|+
|'''Role'''
|'''Description'''
|-
| Developer || Anyone who wants to participate in qa-tools development
|-
| VCS Maintainer || Component owner who has commit rights in version control system (VCS)
|-
| Package Maintainer || Integrator whose responsibility is the OBS packaging
|-
| Release Management || Third party who is responsible of trunk:testing releases(?)
|}

[[File:Release.png]]

Kivio file: [[File:Release.flw]]

# Developer creates merge request(s) in gitorious.
# VCS Maintainer tests and accepts merge requests.
# VCS Maintainer checks/updates change logs.
# VCS Maintainer tags a version.
# VCS maintainer sends email to [http://lists.meego.com/pipermail/meego-qa/ meego-qa mailing list] based on the following template
Topic: Integration request: package-name version
PACKAGE: package-name
TAG: tag name
URL: link to sources
CHANGES: short description of changes containing bugs.meego.com bug numbers of fixed bugs
# Package maintainer updates the OBS package.
# Package maintainer tests the OBS package.
# If the package belongs to tools:testing and passes testing, Package Maintainer may accept it. If the package belongs to trunk:testing, Package Maintainer creates a promotional request to Release Management. (If the package belongs to both repositories, we let the Release Management set bugs fixed by the package to RELEASED state).
# Host side tools are updated to tools:testing after verifying functionality
# Package maintainer replies to meego-qa list about the actions done with the updated package. e.g. 'Updated in devel:quality and sent promotion request to testing'
# Release Management accepts the package. Or not. (Follow meego-packaging and meego-commits.)

''' YouTube videos '''

YouTube is a good way to communicate new features. You can find existing demo videos on [http://www.youtube.com/user/meegoqatools meegoqatools channel on Youtube].

If you shoot a video to YouTube, promote it on meego-qa mailing list!

You can find some hints how to shoot, edit, and upload a video here: [[YouTube_Hints]]

=== Release checklist ===
To make sure fixes are released without delay, check that the following conditions are met

# Change logs are updated and contain relevant references to MeeGo bugzilla
# Created obs request include fixes bug numbers from MeeGo bugzilla
# Bugzilla items listed in changes are set as resolved
# Spec file matches [[Packaging/Guidelines|MeeGo packaging guidelines]]
# Rpmlint warnings are either fixed or explained by comments in the spec file. e.g. eat packages install files into root's home and the reasoning for it needs to be explained
# Host side tool packages use the same source tar ball to produce debian and rpm packages

== Roadmap ==

These are the items that we're currently working on.

The features in the roadmap are followed with META FEA bugs. The features are split to small tool specific FEA:s that block the feature META bug. The META bug is then the last bug to be closed when the feature is finished. You can also follow the tool bug progression from the dependency trees of the META bugs.

Adding a new feature to the roadmap:
# Add a feature bug describing the main purpose of the feature with META and FEA tags.
# Add separate bugs for each tool specific change
# Add correct dependencies between tool specific bugs (e.g. testrunner bug depends on testrunner-lite bug that depends on test-definition bug...)
# Make all of the bugs block the META bug

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12980&hide_resolved=0 Measurement support]
|-
| [[Quality/QA-tools/OTS/Roadmap|OTS releases]]
|}

== Future development ==

The focus is currently on [[ARM/N900/QA|N900 Developer Edition QA]]. Hence the N900 related list below doesn't have a comprehensive information about target builds or priorities. The items listed here are not currently worked on but are planned to be implemented in the long run.

A list of defined features:

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/show_bug.cgi?id=12810 Easy install]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12454&hide_resolved=0 Parallel testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12981&hide_resolved=0 Events feature in automatic testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12937&hide_resolved=0 MCTS coverage support]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12833&hide_resolved=0 Test environment validation]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=13092&hide_resolved=0 Test equipment control]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12971&hide_resolved=0 Qt Creator integration]
|-
| [https://bugs.meego.com/show_bug.cgi?id=13190 A tool that combines Testrunner and Testplanner]
|}

== Design/ Planning ==

* [[Quality/QA-tools/MCTS test automation design|MCTS Test Automation]] (QA Tools support for MCTS)

== Documentation ==

Please make sure that all the relevant documentation regarding the tools is kept up-to-date whenever you update any of the tools. Please consider the end users of the tool as the primary readers of the documentation and make the documentation task-oriented for end user needs. Separate developer documentation can exist as well.

'''Wiki guidelines'''

Every tool should have a wiki page that contains at least 1) Overview of the tool and its benefits 2) Installation instructions 3) Basic use tutorial 4) Contact information.

Make sure that you are familiar with [[Wiki contribution guidelines|MeeGo wiki contribution guidelines]] before creating new content. Currently, there are quite a lot problems relating to e.g. page names, wiki links, deep hierarchies and obsolete pages in our wiki section.

'''Documentation checklist'''

The following table lists the tool-specific documentation that should exist (marked with 'x'). These should be checked frequently and more in depth in the future. Bugs will be filed for the missing or inaccurate documentation (marked as 'NOK' i.e. "Not OK").

{| border="1" cellspacing="0"
|+
|'''Tool''' ||'''Doxygen'''||'''Help''' ||'''Man pages''' || '''Wiki'''
|-
| test-definition || || || || x Checked: asinnela 2011-03-03
|-
| testrunner-lite || x || x Checked: asinnela 2011-03-07 || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14074 Bug 14074] || x Checked: asinnela 2011-06-07
|-
| Testrunner || x || x Checked: asinnela 2011-03-07 || || x Checked: asinnela 2011-03-07
|-
| Testplanner || x || x Checked: asinnela 2011-03-10 || || x Checked: asinnela 2011-03-07
|-
| eat - enables automated testing || || || || x Checked: asinnela 2011-03-08
|-
| OTS - Open Test System || x || x || x || x Checked: asinnela 2011-03-25
|-
| MIN test framework || x || x || x ||
|-
| Scripts and utils || || || || x Checked: asinnela 2011-03-11
|-
| MeeGo Fast Feedback Testing || x || x || || x Checked: asinnela 2011-03-11
|-
| Qpid C wrapper library - libcqpid || x || || || x Page created, content to be added.
|}

'''Other documentation'''

* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]
* [[Quality/QA-tools/How_to_set_up_repositories|How to set up the repositories that are needed to install QA tools]]

== Meetings ==

All meetings will be held in <code>#meego-meeting</code> on <code>irc.freenode.net</code>.

* Team meetings
** QA-tools weekly meetings are held on every Tuesday 08:00 UTC in #meego-meeting2 on irc.freenode.net (please note the "2") from May 3rd 2011 onwards.
** [[Quality/QA-tools/Meetings|Meeting agendas and minutes]]

* Architecture meetings
** Architecture meetings will be held on-demand basis.
** [[Quality/QA-tools/Arch-Meetings|Meeting agendas and minutes]]

* Workshops
** Face-2-face meetings within the team.
** [[Quality/QA-tools/Workshops|Meeting agendas and minutes]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
** Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
** [http://timoph.fi/qa-tools-stats/ Old #meego-qa-tools statistics]
** [http://timoph.fi/qa-tools-logs-archive/ Archived #meego-qa-tools logs]
* Gitorious team, http://meego.gitorious.org/meego-quality-assurance/
* [http://www.youtube.com/user/meegoqatools Youtube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]
* MeeGo OBS - devel:quality
* This wiki area
* [[Quality/QA-tools/ServiceOS|ServiceOS]]
* [[Quality/QA-tools/PXEInstall|PXEInstallation]]

== Team members ==

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
| '''Name'''
| '''Role'''
| '''Affiliation'''
| '''IRC nickname'''
|-
| Riku Halonen || Team member || Nokia || rikhalon
|-
| Kari Sievi || Team member || Digia || sievi
|-
| Timo Härkönen || Team member || Digia || timoph
|-
| Carol Rus || Team member || Digia || carrus
|-
| Sami Lahtinen || Team member || Digia || slahtinen
|-
| Raimo Gratseff || Team member || Digia || rrraimo
|-
| Kyösti Ranto || Team member || Digia || kyranto
|-
| Joonas Kylänpää || Team member || Digia || Kaadlajk
|-
| Timo Mäkimattila || Team member || Digia || timakima
|-
| Elias Luttinen || Team member || Digia || eluttine
|-
| Ville Niutanen || Team member || Digia || Villen
|-
| Vesa Poikajärvi || Team member || Digia || vesse
|-
| Alexey Kuznetsov || Team member || Digia || alkuznet
|-
| Daniil Chuiko || Team member || Digia || dachuiko
|-
| Jarmo Savinen || Team member || Digia || jasavi
|-
| Sampo Saaristo || Team member || Sofica || sampos
|-
| Ling Yu || Team member || Intel || -
|-
| Jing Wang || Team member || Intel || -
|-
| Tuomo Mäkinen || Team member || Ixonos || -
|-
| Jouni Leppäkases || Team member || Ixonos || jouni
|-
| Jarno Keskikangas || Team member || Leonidas || jakeskik
|-
| Janne Hietamäki || Team member || Leonidas || _janne
|-
| Sami Hangaslammi || Team member || Leonidas || sahangas
|-
|}

 
[[Category:QA]]

Quality/QA-tools

2011-08-09T04:43:07Z

Asinnela: /* Tools and other utilities */ Removed a link to empty page

= Quality assurance (QA) tools =

''' We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there. '''

[[File:Tool_meegon.png|400px]]

Quality Assurance tools are developed to ensure MeeGo SW quality. QA tools team develops and maintains tools for quality assurance.

* "Open source tools – available for all, available for development and contributions. Make people accountable for quality."

'''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|QA tools development]] page. We apologize for any inconvenience. The target is to make this page clearer and more informative for the actual users of QA tools.

== Overview ==

QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the figure below. In addition, there are also a couple of concept videos available at our [http://www.youtube.com/user/meegoqatools YouTube channel]:
* [http://www.youtube.com/watch?v=WdXBqGdLz8I Tool offering for manual testing]
* [http://youtu.be/Ry4MM-CX2b8 Test automation]

[[File:Meego-qa-tools.png|600px]]

== Tools and other utilities ==

If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]].

'''Test tools'''

Each wiki page will contain more detailed description, installation instructions and tutorial on the basic usage. For now, please [[Quality/QA-tools#Collaboration spaces|contact us]] if you need help. Currently, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, Meego-ai, libcqpid, eat and MIN from Tools:Testing repository. The instructions for setting up the repositories can be found [[Quality/QA-tools/How_to_set_up_repositories|here]].

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device graphical front-end for sending core dumps produced by rich-core to core dump data base
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|-
| [[Quality/QA-tools/CrashReports|Crash Reports Web UI]] || Web UI for Crash Reports
|-
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance
|-
| [[Application Monitor]] || Monitor runtime indicators - CPU, memory, power for specified apps
|-
| [[System Monitor]] || Tool to monitor whole system status.
|-
| [[Power Diablo]] || Comprehensive and configurable power-sensitive workload.
|-
| [[Video performance]] || Collect FPS, CPU information when do video playback
|-
| [[TimedLaunch]] || Precisely collect application launch time automatically
|-
| [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || Test cases and Cucumber steps for MeeGo QML UI applications
|-
| [[Testkit_Howto|testkit-lite]] || python based test framework, command line tool, supporting test definition xml
|-
| [[Testkit_Howto|testkit-manager]] || web based test tool with fancy UI, supporting both manual and auto testing remotely
|}

'''Other utilities'''

{| border="1" cellspacing="0"
|+
|'''Name (link to wiki page)''' ||'''Short description'''
|-
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||
|-
| [[Quality/QA-tools/rich-core|Rich core dumper (sp-rich-core)]] || A tool to collect core dump and context data from process crashes
|-
| Crash Reporter settings || Settings package for Crash Reporter
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] ||
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] ||
|-
| Service OS based Flasher || Flasher to support Intel netbook/tablet
|-
| [[Environment collector]] || Collect detail system environment information
|-
| [[Memory eater]] || A small memory tool to measure system memory by eat memory Mb by Mb till swap happen
|-
| [[CleanPowerCycle]] || Repeatedly reboot device with specified times and wait time
|-
| [[Quality/QA-tools/Corelysis|Corelysis]] || A daemon to process rich core dumps in the back-end server
|}

'''Tools and utils not in active development'''

Tools listed here are in maintenance and no new features are planned to be implemented in the near future to them.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || Test execution tool with graphical UI
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] || Simple tool for creating and editing test plan files
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] ||
|-
| [http://min.sf.net/ MIN Test Framework] || Advanced test framework
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] ||
|-
| Qpid C wrapper library - libcqpid ||
|}

== Feature requests and bugs ==

Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=ASSIGNED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance Assigned bugs and features - Working on it]
* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order]

Bugzilla instructions:
* [[Quality/How To Report Bugs|How to report bugs]]
* [[Quality/Bug Life Cycle and Handling|Bugzilla workflow]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
* [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]

== Nice to have ==

None of the existing tools answer your needs? Here is where you should enter any suggestion.

* Relieve localization testing effort by automating all or part of it ([[Quality/QA-tools/Automation of L10n testing|Detail]]).

* We may consider the need to have a fully functional test cases management system that could be widely used by the community to create/update test cases ([[Quality/QA-tools/TCMS|Detail]]).

 
[[Category:QA]]

SDK/Docs/1.0/Getting started with the MeeGo SDK for Linux

2011-08-08T18:14:55Z

Asinnela: Wiki link fixes and replacing links to deleted pages

== Introduction ==

The MeeGo SDK for Linux includes the following in a single download image:

* A MeeGo QEMU virtual environment, which boots the MeeGo OS in a virtual machine and shows the UI in a window on your Linux workstation
* A MeeGo chroot (change-root) environment, based on [http://www.freedesktop.org/wiki/Software/Xephyr Xephyr], with some scripts to start/stop a MeeGo desktop inside Xephyr, and Qt Creator, which can be configured to deploy to remote MeeGo devices
For information on these debugging environments, see [[SDK/Docs/1.1/MeeGo developer story|MeeGo SDK options]]. For problems with any of these steps, see the [[MeeGo_SDK_Troubleshooting|Troubleshooting page]].

== Pre-requisites ==

To use the MeeGo SDK, you should be running a reasonably modern Linux distribution (such as [https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 10.04 LTS], [http://www.opensuse.org/en/ openSUSE 11.3]) on reasonably modern hardware, such as:

* CPU: 32bit Intel Atom or Intel Core 2 CPU

In addition:
* QEMU requires that your system have Virtualization (VT) support for graphics acceleration. Check the [[MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration page]] to ensure your system is capable. 
* Xephyr requires that your system have an Intel graphics chipset.

== Download the MeeGo SDK Image==
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>Image Type</th><th>Size</th><th>File</th><th>MD5SUM</th></tr>
<tr><td>Netbook (July 27)</td><td>518MB compressed 3.1GB uncompressed</td><td>[http://download3.meego.com/sep09/meego-netbook-ia32-1.0.80.12.20100727.1-sdk-pre0901.raw.tar.bz2 meego-netbook-ia32-1.0.80.12.20100727.1-sdk-pre0901.raw.tar.bz2]</td><td>Compressed: f1645655e488b6faecd5c951ae75dd04 Uncompressed: 9c8f3aac4e4ba7c1cb746662feee8a15</td></tr>

<tr><td>Handset (Oct 12)</td><td>778MB compressed 3.1 GB uncompressed</td><td>[http://download3.meego.com/meego-handset-sdk-20101012-1.1.80.20101024.1603-sda.raw.tar.bz2 meego-handset-sdk-20101012-1.1.80.20101024.1603-sda.raw.tar.bz2]</td><td>Compressed: 0fd8f29934666a94498d7806495e1e3d 
Uncompressed: c868117be931509306682d091a0d094c</td></tr>
</table>

Building From Source: For information on building qemu-gl and the above images from source, see the [[SDK/Docs/1.1/Building QEMU Tools|QEMU tools page]].



== Setup QEMU or Xephyr ==

Once the SDK image is downloaded and unpacked, follow the instructions on either of the following pages:

* [[SDK/Docs/1.1/Building_QEMU_Tools|Setting up MeeGo SDK with QEMU]]
* [[MeeGo_SDK_with_Xephyr|Setting up MeeGo SDK with Xephyr]]
 

== Another language version of this page ==

* [[在 Linux 上使用 MeeGo_SDK|Simplified Chinese - 简体中文]]

[[Category:devguide]]
[[Category:meego-1.0]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]

Quality/QA-tools/OTS/Troubleshooting

2011-08-08T18:08:11Z

Asinnela: /* Usage */ Wiki link fix

= Troubleshooting =

This troubleshooting guide aims to help with OTS installation and usage.

''Please remember that OTS is at a relatively early stage in its development and evolving rapidly and whilst every effort is made to keep all the documentation up-to-date there will be some inevitable time lag.''

== Related Documents ==

* The [[Quality/QA-tools/Autotest-guide#Troubleshooting|Autotest Troubleshooting Wiki]]

== Basic Principles ==

This section suggests how you can apply simple fault-finding techniques to OTS...

=== Look in the logs ===

OTS offers extensive [[Quality/QA-tools/OTS/Logging | logging options]]

=== Locate and breakdown the problem ===

OTS is a highly modular system. Most of the Components are designed to be run as tools in their own right. They have command line interfaces and can be run independently.

A basic understanding of the [[Quality/QA-tools/OTS/About|Architecture]] and the responsibilities of the [[Quality/QA-tools/OTS/Components|Components]] should guide you through it.

There is generally documentation for each of the Components and illustrations on how the the individual tool is run. It is all Open Source, nothing is hidden!

== Reporting Problems ==

=== What version am I running? ===

Assuming you have installed the OTS component you can check the version as follows:

$python

<code>
>>> import ots.worker
>>> ots.worker.__VERSION__
'0.8r0.0.1-338-gdbe7dev'
>>>
</code>

=== Is it a known issue? ===

Check the [http://bugs.meego.com/buglist.cgi?component=ots&product=Development%20Tools&query_format=advanced&title=Bug%20List:%20ots&ctype=atom OTS bug tracker]

== Installation ==

If you have been following the [[Quality/QA-tools/OTS/UserDocumentation/Installation|Installation Instructions]] and still run into problems then you might benefit from the [[Quality/QA-tools/OTS/DeveloperDocs#DivingIn|Developer Documentation]]. The Developer Documentation show how the Unit Tests and Component Tests are run. If the unittests or component tests are failing then the tracebacks should give an indication as to what the problems are.

== Usage ==

If there is a problem in running your test(s). Then once again the logs are a good place to start of which the http logger is the most user friendly. The Exception and traceback should give an indication of the problem. Check what any [[Quality/QA-tools/OTS/ErrorCodes|error code]] means that might give you a clue.

== FAQs ==

=== Where are my testruns? ===

If you are firing runs and they don't appear to be taken by the worker it is worth looking at the Queues. This service is provided by RabbitMQ and the [http://www.rabbitmq.com/man/rabbitmqctl.1.man.html rabbitmqctl] tool is a useful aid.

=== Where are the Prerequisits for the Host? ===

Instructions for key authentication and dependent packages are all dealt with in this [[Quality/QA-tools/Autotest-guide#Setting_up_test_automation_environment|wiki]]

=== Why doesn't my device flash? ===

Flashing can work intermittently with some Architecture / Image combinations. It can also be a time consuming process so a certain degree of patience is required. There are some [[Quality/QA-tools/OTS/UserDocumentation|notes]] on flashing here that should help pinpoint the problem. Unfortunately there is always a chance that even if you have things set up correctly and it won't work first time - so try again.

=== Why won't my host allow me to connect to the device? ===

Any hardware control operation that requires USB will require the permissions to be set appropriately.

e.g. By following [[Quality/QA-tools/OTS/UserDocumentation/Conductor#Setting_your_USB_permissions_for_Flashing|these]] instructions for flashing you can avoid root access for the Flasher and all the dependent modules (Conductor and Worker)

=== Why won't OTS trigger work? ===

You might have an error such as this:

<code>
ProtocolError: <ProtocolError for localhost/xmlrpc/: 500 Internal Server Error>
</code>

Is your using Apache is it set-up properly? - Check the apache logs, your apache2.conf file and DJANGO_SETTINGS_MODULE.

The [[Quality/QA-tools/OTS/Plugins/HTTP_logger | HTTPLogger]] instructions give instructions on server configurations

Not forgetting to restart Apache if there are any changes.

<code>
sudo /etc/init.d/apache2 restart
</code>

Quality/QA-tools/Test packaging

2011-08-08T18:07:16Z

Asinnela: /* Test plan definition */ wiki link fix

== Introduction ==

Test packaging is intended to provide flexible and consistent ways to run tests and get results. You may select testing tools of your choice.

Test packaging is set of simple rules to wrap tests with test plan inside rpm package. Tool support for validating test plan and automating test plan execution is provided with testrunner. Following describes rpm-version of test packaging.

== Open Testing Service Architecture ==

The context of test package usage is described in [[Quality/QA-tools/OTS|Open Testing Service (OTS) architecture]].

== Test packaging rules ==

A source package with test cases must:

* build binary rpm package with name which ends with "<code>-tests</code>" (this is a test package)

A test package must:

* contain all tests, scripts and configuration files required to run tests
* define dependencies - the ones it tests, the test tools and test data it depends on (if any)
* contain test plan located at <code>/usr/share/<packagename>-tests/tests.xml</code> [1]

For details on creating a test package, see [[Quality/QA-tools/Test package|Creating a test package]].

== Test plan definition ==

<code>tests.xml</code> describes what test cases this package has. The file must conform to the specification described in [[Quality/QA-tools/Test plan|Test Definition XML]].

Here are values for some of the key fields:
* Level: <code>[Component|Feature|System|Product]</code> - Most common ones for the Meego.com QA use are the Feature (for feature acceptance tests agreed with product management) and System (for Use Case based system tests). Projects might use Component value for the component and component integration tests.
* Type: <code>[Functional|Integration|Performance|Benchmark|Resource utilisation|Throughput|Latency|Framerate|Robustness|Iterative|Low-resource|Long-lasting|Recoverability|Usability]</code> - This is now hybrid of test areas and types currently in use (see [[Quality/TestAreas|Test areas]]). (Component) Integration testing might be the one on which Projects and Release Engineering are having interest.
* Domain: <code>[Security|Data Management|Software Management|System|Location|Kernel|Personal Information Management|Multimedia|Essentials|Communications|Qt|Graphics]</code> - This is now aligned with architectural domains (see [http://meego.com/developers/meego-architecture/meego-architecture-domain-view MeeGo architecture domain view]).
* Component: <code>[Accounts|Single Sign-On|Integrity Protection Framework|Certificate Manager|Software Distribution Security|Access Control Framework|Security Adaptation|Content Framework|Package Manager|System Control|Resource Policy|Startup Services|Context Framework|Sensor Framework|Sensor Adaptation|Device Mode Adaptation|Haptics and Vibra Adaptation|Location Framework|Location Adaptation|Linux Kernel|Calendar Engine|Contact Engine|Email Engine|Backup Framework|Synchronization Framework|Imaging and Video Adaptation|Camera Adaptation|UPnP|Gstreamer|Audio Adaptation|Pulse Audio|Base Essentials|IP Telephony|Instant Messaging|Presence|Cellular Framework|ConnMan|Bluetooth|Communication Adaptation|Qt|Qt Mobility|Qt Webkit|Web Runtime|Font Management|Input Adaptation|X11|OpenGL ES|Display and Graphics Adaptation]</code> - This is now aligned with architectural components (see [http://meego.com/developers/meego-architecture/meego-architecture-domain-view MeeGo architecture domain view]).
* Feature: List of numeric values of the Bugzilla Feature IDs, which test case is validating (e.g. 11111,22222). IDs enable mapping of features and tests in qa-reports.meego.com.
* Requirement: ''Deprecated'' - provided for backward compatibility but not to be suppored by Testplanner editor.

== Tool support ==

OTS takes care of automated testing with test packages in cloud. Highest level of automation in this context means one-button test automation triggered with version control update, ending up in test run results in target hardware published.

Tool chain covers all the bits and pieces required for that.

SDK/Meetings/20110223 Weekly

2011-08-08T17:58:52Z

Asinnela: Wiki link fixes

= MeeGo SDK Weekly Meeting 20110223 =

This document contains agenda and minutes (added after the meeting) of SDK weekly telco meeting on 20110209 07:30 EEST.

== Conventions of this document ==

* AP: = Action point agreed on this meeting
* yyyymmdd AP: = Action point agreed on previous meeting
* yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
* yyyymmdd AP DONE: = Action point done
* yyyymmdd AP CANCELLED: = Action point cancelled
* AGREE: = Item that has been agreed by the team
* POSTPONED: = Agenda item postponed from last meeting
* OLD: = Info from previous meeting (delete during the meeting)

== Attendees ==

*

== Agenda ==

=== SDK Program (Veli) ===

* Nokia changes...
* MeeGo Conference May 23-25 (San Fran)
* 20101215 AP: What is the date of Open source of IFW? (Maurice)
** Everything seems to be clear
** [Bob asking:] Is this the basis for the "super installer" future? Is that still going to happen? Maurice: Yes. Standard practice accepting contributions as Qt.
** Deadline next week
* Bob http://appdeveloper.intel.com/en-us/meego-sdk-suite

==== Features (Ville) ====

* Proposal: rework the entire feature mess to be better aligned with reality, more easily browsable and maintainable.
** Create a two-level hierarchy of items, and use the description field better to place an individual feature within the hierarchy.
** Top level items:
*** SDK m(aintenance)
*** Target m(aintenance)
*** Project m(aintenance)
*** Create
*** Build
*** Test
*** Publish
*** Host support
** Every requirement is to be placed within that hierarchy, and renamed to reflect its position, and linked to the appropriate components (the component list is outdated, and the one used in the bugs shall be taken into use, and expanded as needed).

** Immediate steps (right here, right now):
*** Agree that the set above is a decent enough working assumption.
*** Open issue: documentation - shall a separate top level item be created for it, or will all documentation-related items be folded into the appropriate items (in which case something along the lines of "SDK productization" is probably required: release notes, installation instructions and generic documentation does not have a good home in the above).

** Next steps (by the workshop next week):
*** Rework the entire current set into the new form, renaming features as needed.
*** Add features as potential content.
*** Review the set in Helsinki (Thursday or Friday), especially tagging things out of 1.2 as realistic.

** Steps after that
*** Roll in the comments from the workshop.
*** Cross-link to internal requirements DB.
*** Request comments from the other programs (this set is extremely handset-centric).

=== Architecture (Bob) ===
(Meetings held weekly, as needed)

* [[SDK/Architecture|Architecture]]

Topics for future meetings:
* How to speed up MeeGo SDK
** Install (reduce size, target/sysroot management)
** Deploy/debug (QEMU acceleration, deploy w/o packaging, etc)
* rsync: Using QEMU files for sysroot
** [[SDK/Sysroot_extension|Sysroot extension]]
* Release process (discussion started)
* Windows builds (server - http://bugs.meego.com/show_bug.cgi?id=11762, process)
* How to identify the installed MeeGo SDK version (registry key, file, gconf)

Covered in past weeks (Resolutions here: http://piratepad.net/qqICWdiYLl )
* Thurs 20th Meeting
** Package group - list of devel packages in sysroot
*** Study on [[SDK/Packages_group|Packages group]]
** Qt Creator rc1 promotion and QA

* Thurs 13th Meeting
** Accomodate 3rd party libraries in addition to sysroot on Windows and Linux
** Feature 10949 - [FEA] Make the installation of MeeGo SDK for Linux easier http://bugs.meego.com/show_bug.cgi?id=10949

** AP: Add minutes to: [[SDK/Meetings|Meetings]] (Bob) DONE.

=== Releasing (Fathi) ===

* Fedora 14 support added
* Toolchain broken on Fedora 14
* Qt Creator 2.1.0 released - to be integrated
* Random images broken regularly
* qemu-arm and qemu-gl merge in progress
* kmod-kfgles2 broken with kernel 2.6.37
* Qt Simulator to review and promote

=== Windows port (Max) ===

* Winchow is working on update toolchain.
* Window server available at OSU
** TODO: set up Windows server (Al, Max)
* TODO: Attica/OBS plugin to build only (skip usability for now)
* TODO: reduce the size of Qt Simulator built

=== Mac OS X port (David) ===

* David Lawlor started in Portland, OR (Intel) on Jan 31st.
* Mac server available at OSU
* ARM toolchain available
* Beta desired for MeeGo 1.2 (release in May).
* Intel guess at release is July. But scoping work is just starting.

=== Toolchains (Jarmo) ===

* Still some changes done to communication wiki. Hopefully can be published this week.
* There is a silicon bug in Cortex-A8 (also in N900) which prevents the use of Thumb2 instructions ( http://cateee.net/lkddb/web-lkddb/ARM_ERRATA_430973.html). Therefore only NEON optimized toolchain can be used in the N900 reference.
* Juha Kallioinen proposed to be the next Toolchain Lead
** AGREED

=== Documentation (Taru) ===

* Taru Laine is the doc team lead.
* Weekly documentation telco meetings have been postponed for now and will be restarted in March closer to the April release date.
* Documentation backlog for MeeGo 1.2 SDK can be found [[Documentation_Backlog_for_MeeGo_1.2|here]]
* AP Taru DONE: To have a meeting with Tiffiny Rossi (responsible for designing the content for the developer.meego.com site) to discuss how to streamline our processes for creating MeeGo-related content and the documentation plans for MeeGo 1.2 SDK (schedules and content)
** Main points from the meeting:
*** SDK developer documentation will be published in Developer.meego.com. The content of the site will consist of MeeGo 1.1 SDK developer documentation until MeeGo 1.2 SDK is released. After MeeGo 1.2 release, MeeGo 1.1 SDK content could be stored and maintained in the [[Main Page|wiki]].
*** AP Taru: Invite Tiffiny to the MeeGo SDK documentation team meetings that will be restarted on week 9.
* Unresolved issues to discuss with the SDK team:
** Documentation team members for next week's meeting.
** New feature hierarchy and its impacts on documentation
** Community contribution for MeeGo 1.2 documentation, especially for ''Instructions and best practices'' and ''Sample applications''.
** Finding owners for the following tasks: Device provisioning instructions for netbook, Netbook UI guidelines, Debugging instructions for MeeGo 1.2 SDK (currently part of Other documentations feature), Creating a Hello world application (currently part of Other documentations feature), Instructions for building MeeGo image/QEMU image (currently part of Other documentations feature)
** Timetable for MeeGo 1.2 SDK developer documentation features (based on the milestones assigned for the MeeGo 1.2 SDK features)

=== QA (Juha) ===

* All QA reports at http://qa-reports.meego.com/
* Feature status :
** Released :
*** total 5
*** testability checked 3
*** test case exists 3
*** under work 1
** Resolved :
*** total 39
*** testability checked 31
*** test case exists 20
*** under work 2 (+ OBS related cases are waiting for more information)
** Accepted :
*** total 108
*** testability checked 7
*** test case exists 3
* Testing
** Updated tools on Ubuntu 10.10 64bit and Fedora13 32bit will be tested with latest available sysroot (meego-core-armv7l-madde-sysroot-1.1.90.4.20110222.2).
*** The bug [[https://bugs.meego.com/show_bug.cgi?id=13399 #13399]] about rpm creation on both distros is still valid.
*** On Ubuntu bugs [[https://bugs.meego.com/show_bug.cgi?id=12561 #12561]], [[https://bugs.meego.com/show_bug.cgi?id=12853 #12853]], [[https://bugs.meego.com/show_bug.cgi?id=13171 #13171]] and in Fedora14 [[https://bugs.meego.com/show_bug.cgi?id=12561 #12561]], [[https://bugs.meego.com/show_bug.cgi?id=12820 #12820]] are still valid.
* Git repository for testplans requested and will start pushing plans to git when first plans are ready and checked.
* Test transition is still in progress.
* Review test cases on tl (BMC#12536)
* Formalize bug handling workflow

MeeGo FAQ

2011-08-08T17:52:35Z

Asinnela: /* I have a question. Where should I post it? */ wiki link fix

General Frequently Asked Questions (FAQ) about MeeGo.

== Additional FAQs for Specific Topics ==
* [[MeeGo Netbook FAQ]]
* [[ARM/FAQ]]
* [http://meego.com/devices/in-vehicle/in-vehicle-faq In-Vehicle (IVI) FAQ]
* [[MeeGo Distribution Frequently Asked Questions]]

== General ==

=== What is MeeGo, and how can I learn more about it? ===

MeeGo is an open source, Linux project focused on netbooks, handheld computing and communications devices, in-vehicle infotainment devices, connected TVs and other small form factor devices. MeeGo is a Linux Foundation project that brings together the Moblin project, headed up by Intel, and Maemo, by Nokia, into a single open source activity. Learn more about MeeGo by visiting our [http://meego.com/about About] page.

=== What is the governance for the open source MeeGo project? ===

The Technical Steering Group sets the direction, tone, and vision for MeeGo, speaks on behalf of the project, and is responsible for project level decisions and overall leadership. Much like most open source projects governed by a benevolent dictator, the MeeGo project is led by Imad Sousou and Valtteri Halla. The complete governance, project structure and roles can be found on our [http://meego.com/about/governance Governance] pages.

=== Why doesn't MeeGo run on my hardware? ===

The simple answer is that doesn't run on your hardware '''yet'''. Right now, MeeGo runs on a limited number of hardware configurations (see above sections for details). This is a common approach for open source software. The person or people who write the first version of the software selects a subset of hardware to get the project started. For example, the [http://www.linux.org/people/linus_post.html first version of the Linux kernel] available to the public only ran on a 386 with AT drives, because that was what Linus Torvalds had at the time. If the open source project is successful (as Linux has been) more and more people will begin contributing ports of the software to additional hardware platforms. Linux now supports many different hardware configurations because people were willing to put in the time to add them.

The best way to get support for your hardware is to either write it yourself and submit patches to MeeGo or convince someone else to support your hardware (maybe your hardware vendor). You can also [http://bugs.meego.com/ file it as a feature request] and hope that someone decides to work on it.

MeeGo will eventually support a broader set of hardware, but it will take time and contributions from the community to make it happen.

== Community and Participation ==

=== I have a question. Where should I post it? ===

There is a good chance that someone has already asked a similar question. Before submitting a new question, please take the time to do a quick '''search''' through our [http://forum.meego.com/ forums], [http://meego.com/community/mailing-lists mailing lists], [http://meego.com website] and [[Main Page|wiki]] before asking a new question.

* '''Users and General Questions''': If you are using MeeGo, but are not actively involved in MeeGo development, please post in the '''[http://forum.meego.com/ Forum]'''. Questions about support for specific hardware, installing MeeGo or other questions that don't involve looking at the code, you should start with the forum.
* '''Application Developers''': If you are writing applications that will run on MeeGo or for questions about the API, SDK or related topics, you can post those in the '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-SDK mailing list]''' or in the '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer forum]''', either are fine.
* '''Community''': Questions about the MeeGo community, participating in MeeGo or other general community questions can be posted in the '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community mailing list]''' or in the '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters forum]'''.
* '''Developers for the MeeGo platform''': Please do not post in the [http://lists.meego.com/listinfo/meego-dev MeeGo-Dev mailing list] unless you are working on MeeGo architecture or development of components included in the MeeGo release.

You can learn more about our various mailing lists, forums, IRC channels and more by visiting the [http://meego.com/community community] page on the website.

=== Are there regular meetings that I can attend? ===

The [[Technical Steering Group meetings]] are our primary governance meetings and are open to anyone who wants to attend. Many of the teams involved in MeeGo also have regular meetings on IRC. We have a [[MeeGo-Meeting IRC Schedule]] where you can find information about our meetings.

=== How can I contribute to MeeGo ===

There are many ways for people to contribute to MeeGo, and you don't need to be a programmer to participate. We have a [[Contributing to MeeGo]] guide with more details.

=== I want to help edit the wiki. Do you have guidelines or instructions? ===

These [[Wiki contribution guidelines]] will help you get started.

== Developers ==

=== Where can I find information about developing MeeGo applications? ===

The [http://meego.com/developers developers section of the MeeGo website] contains information about our architecture, API, SDK and other useful documentation for application developers. The [http://meego.com/developers/getting-started Getting Started] page has links to download the SDK and other introductory information.

=== How can I get access to the MeeGo build system or learn about building a MeeGo distribution or MeeGo packages? ===

Information about our build infrastructure, including a community build system, can be found on our [[Build Infrastructure]] wiki page. You might also be interested in our [[Image Creation]] instructions.

=== I want to download/mirror MeeGo locally ===

See [[Meego_IT/Mirrors]] for information about how to mirror repo.meego.com over rsync.

== Other Resources ==

* [[Glossary]]
* [http://meego.com/downloads Download MeeGo]
* [http://meego.com MeeGo.com]

[[Category:Beginner]]

Web infrastructure

2011-08-08T17:50:29Z

Asinnela: /* MeeGo Services */ Wikified wiki links

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|OSU
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|OSU
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|[[Main Page|http://wiki.meego.com]]
|MediaWiki 1.16.2
|OSU
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|OSU
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|[[Quality/Error_Management|details]]
|-
|http://apidocs.meego.com
|Static HTML/files
|OSU
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|OSU
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|[[Mailing list guidelines|details]]
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|[http://meego.com/users/reggie Reggie Suplido]
|[[Web_infrastructure/Forum|details]]
|-
|http://planet.meego.com
|Midgard
|OSU
|active
|[http://meego.com/users/bergie Henri Bergius]
|[[Web_infrastructure/Planet.meego.com|details]]
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|[http://download.meego.com download.meego.com]
|Generic Web Server, Serves Intermediate Builds
|OSU
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|OSU
|active
|[http://meego.com/users/jennycao Jenny Cao]
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|-
|ots.meego.com
|http://gitorious.org/qa-tools/ots
|OSU
|Decomissioned
|
|[[Quality/QA-tools/OTS|details]]
|}

Quality/QA-tools

2011-08-08T07:29:06Z

Asinnela: /* Tools and other utilities */ Wiki link fixes

= Quality assurance (QA) tools =

''' We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there. '''

[[File:Tool_meegon.png|400px]]

Quality Assurance tools are developed to ensure MeeGo SW quality. QA tools team develops and maintains tools for quality assurance.

* "Open source tools – available for all, available for development and contributions. Make people accountable for quality."

'''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|QA tools development]] page. We apologize for any inconvenience. The target is to make this page clearer and more informative for the actual users of QA tools.

== Overview ==

QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the figure below. In addition, there are also a couple of concept videos available at our [http://www.youtube.com/user/meegoqatools YouTube channel]:
* [http://www.youtube.com/watch?v=WdXBqGdLz8I Tool offering for manual testing]
* [http://youtu.be/Ry4MM-CX2b8 Test automation]

[[File:Meego-qa-tools.png|600px]]

== Tools and other utilities ==

If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]].

'''Test tools'''

Each wiki page will contain more detailed description, installation instructions and tutorial on the basic usage. For now, please [[Quality/QA-tools#Collaboration spaces|contact us]] if you need help. Currently, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, Meego-ai, libcqpid, eat and MIN from Tools:Testing repository. The instructions for setting up the repositories can be found [[Quality/QA-tools/How_to_set_up_repositories|here]].

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device graphical front-end for sending core dumps produced by rich-core to core dump data base
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|-
| [[Quality/QA-tools/CrashReports|Crash Reports Web UI]] || Web UI for Crash Reports
|-
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance
|-
| [[Application Monitor]] || Monitor runtime indicators - CPU, memory, power for specified apps
|-
| [[System Monitor]] || Tool to monitor whole system status.
|-
| [[Power Diablo]] || Comprehensive and configurable power-sensitive workload.
|-
| [[Video performance]] || Collect FPS, CPU information when do video playback
|-
| [[TimedLaunch]] || Precisely collect application launch time automatically
|-
| [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || Test cases and Cucumber steps for MeeGo QML UI applications
|-
| [[Testkit_Howto|testkit-lite]] || python based test framework, command line tool, supporting test definition xml
|-
| [[Testkit_Howto|testkit-manager]] || web based test tool with fancy UI, supporting both manual and auto testing remotely
|}

'''Other utilities'''

{| border="1" cellspacing="0"
|+
|'''Name (link to wiki page)''' ||'''Short description'''
|-
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||
|-
| [[Quality/QA-tools/rich-core|Rich core dumper (sp-rich-core)]] || A tool to collect core dump and context data from process crashes
|-
| Crash Reporter settings || Settings package for Crash Reporter
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] ||
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] ||
|-
| Service OS based Flasher || Flasher to support Intel netbook/tablet
|-
| [[Environment collector]] || Collect detail system environment information
|-
| [[Memory eater]] || A small memory tool to measure system memory by eat memory Mb by Mb till swap happen
|-
| [[CleanPowerCycle]] || Repeatedly reboot device with specified times and wait time
|-
| [[Quality/QA-tools/Corelysis|Corelysis]] || A daemon to process rich core dumps in the back-end server
|}

'''Tools and utils not in active development'''

Tools listed here are in maintenance and no new features are planned to be implemented in the near future to them.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || Test execution tool with graphical UI
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] || Simple tool for creating and editing test plan files
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] ||
|-
| [http://min.sf.net/ MIN Test Framework] || Advanced test framework
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] ||
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] ||
|}

== Feature requests and bugs ==

Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=ASSIGNED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance Assigned bugs and features - Working on it]
* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order]

Bugzilla instructions:
* [[Quality/How To Report Bugs|How to report bugs]]
* [[Quality/Bug Life Cycle and Handling|Bugzilla workflow]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
* [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]

== Nice to have ==

None of the existing tools answer your needs? Here is where you should enter any suggestion.

* Relieve localization testing effort by automating all or part of it ([[Quality/QA-tools/Automation of L10n testing|Detail]]).

* We may consider the need to have a fully functional test cases management system that could be widely used by the community to create/update test cases ([[Quality/QA-tools/TCMS|Detail]]).

 
[[Category:QA]]

ARM/N900/QA

2011-08-08T06:45:39Z

Asinnela: Wiki link fixes

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

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [[ARM/N900/Status|General DE N900 Feature status]]
* [[ARM/N900/QA/Performance|Performance results]]
* [http://qa-reports.meego.com/1.2/Handset/Dataflow/N900CE Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Key%20Feature Key Features reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [[MeeGo-Meeting_IRC_Schedule|MeeGo-Meeting IRC Schedule]]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-23-06.58.html Meeting minutes 23-06-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [http://lists.meego.com/listinfo/meego-qa QA-mailing list]
* join #meego-qa at freenode

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|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)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated 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 [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|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 ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de 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 [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ 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.
[[File:backend.png|350px|thumb|right|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 [[Quality/QA-tools/CrashReports/API|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
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]
== Functional Testing ==
====Daily testing====

Acceptance/Sanity test is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance test reflects the most important and basic functionalities of the distribution. We do the acceptance test against Trunk:Testing repo.

*Acceptance (Trunk:Testing)

*Sanity (Trunk:Daily)

====Weekly testing====
This is QA weekly testing cycle for weekly images released by distribution team. Our testing focus would be *Key feature testing* to cover the key features and ensure MeeGo Handset UX delivered features are basically covered and major issues are exposed in timely fashion, as well as changes introduced from the last build do not break working features. The test covers UX and applications (MeeGo Audio player ,Video player, Dialer, SMS, fennec browser,VKB, Email, Photo Viewer, Calendar, IM and contacts, etc).

*Key Basic Testing

*Data Flow Testing

*Basic Feature Testing

==== Execution Process ====

[[File:Process.PNG]]
 

==== Testing images Community Edition image ====
[http://repository.maemo.org/meego/n900-de/daily/ Community Edition images]

[[ARM/N900/Install/MMC#Linux|Flashing Image to MMC]]
* Daily '''Testing''' image called a Acceptance image
* Daily '''Stable''' image called a Sanity image
* Every Monday stable image is called as '''Weekly Image'''

==== Execution ====

*Download Test Sets from gitorious [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests/trees/master Test Sets]
*List all test cases in Excel and create .csv file [http://qa-reports.meego.com/example.csv example csv]
*[[Quality/HandsetUXQAGettingStarted#Spirit_of_Testing|Test cases verdict]]
'''Pass''' = If all the steps and Functionality is as per expected
'''Fail''' = If any of the one step or Functionality is not as per expected
'''N/A''' = If the test cases are not executable due to the absence of related package in the image, the test results should be N/A
'''Blocked''' = This is a special value required in the situations where verdict cannot be given due to failure in preconditions
* Upload Test report to with respective Test cycle in QA reporting tool [http://qa-reports.meego.com/ QA Reporting tool]

====Reporting bugs====
*Bug reporting tool: http://bugs.meego.com/
*Bugs are reported in Bugzilla.
*[[Quality/How_To_Report_Bugs|How to report bugs]]
*Logging new bug
[[File:Newbug.PNG]]
 

====Questions or Doubts====
Any question please leave your query in #meego-arm (irc.freenode.net) or you can [mailto:meego-qa@lists.meego.com meego-qa mailing list]

Suggestion about updating of this page [mailto:srikanth.4.yarlagadda@nokia.com Srikanth Yarlagadda]

Questions about execution and reporting please ping me in IRC srikanth_rst

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|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 ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== 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 ====
* DE testing
* Bug verification
* Wiki clean/update

==== Backlog ====
* Reliability testset planning
* 1.3 Vanilla vs 1.2 DE current measurements
* DE Filesystem benchmark

==== In progress ====
* DE Hourly Automation improvement

==== Done ====
* Qt API test investigation
* Wiki clean/update (waiting for comments)
* Testcase automation list
* 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
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== 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 =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

In-vehicle

2011-08-08T06:15:45Z

Asinnela: /* MeeGo IVI Development Boards */ Wiki link fix

= In-vehicle Infotainment (IVI) =

MeeGo IVI is setting the new standard for in-vehicle infotainment in cars, buses, airplanes, etc. MeeGo IVI is a Free and Open-Source Software (FOSS) OS distribution integrating the MeeGo Core for embedded systems leveraging and extending functionality known from mobile computers and handsets into vehicles. Building on the MeeGo OS Base and the MeeGo OS Middleware the MeeGo IVI software stack enables rich Internet and multimedia experiences to consumers while traveling.

== Organization ==

The MeeGo IVI organization is composed of a Working Group and a Project Team. The Working Group is responsible for the definition of the roadmap and the MeeGo IVI Project Team executes the implementation through the partnering organizations using the best practices of open-source development. Through the collaboration of organizations and companies covering automotive, computer hardware, communications, and software industries this partnership enables jump-starting product development for rapid delivery allowing adopters to concentrate on their core competencies while benefiting from this extensive know-how and the open-source assets.

For a graphical representation of the organizational structure: [[Media:MeeGo_IVI_OrgStruct.pdf]]

=== Working Group ===

The Working Group is composed from the following members and roles:

* Working Group Chair
** Represents and promotes the Working Group.
** Leads strategic discussions on requirements, direction, policies.
** Commitment: full-time role.
** Current Working Group Chair: '''[http://meego.com/users/RudolfStreif Rudi Streif (Linux Foundation)]'''

* Working Group Representative (the number is not limited, others participants to be invited)
** Represents his/her organization in the Working Group.
** Collects, organizes, prioritizes, and contributes requirements from his/her organization.
** Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
** Current Working Group Representatives:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** LG Electronics: '''[https://meego.com/users/hyungjin Hyungjin Jeon]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** co-leads the Project Team and defines the release schedule together with the Project Manager.
** Accountable to the Working Group for delivery of agreed upon requirements.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PDM.pdf]]
** Current Product Manager:

* Program Manager (cross-functional across Working Group and Project Team)
** Works with the Lead Architects and Lead Designers on effort estimates and schedules.
** co-leads the Project Team together with the Product Manager.
** Accountable to the Working Group for deliverables and schedule.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PJM.pdf]]
** Current Program Manager: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

==== Working Group Meetings and Minutes ====
The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|IVI Working Group]].

=== Project Team ===

The Project Team has members with various roles that are subject to change according to the requirements of the current projects. The number of members and roles in the Project Team is not limited and grow as the team gains momentum and takes on larger tasks.

* Lead Architect
** Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
** Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
** Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
** Commitment: > 50% dependent on sub-project complexity.
** Current Lead Architect: '''[http://meego.com/users/tomcounihan Tom Counihan (Intel)]'''

* Lead Designer (multiple roles)
** Responsible for the detailed implementation design of the architecture.
** Estimates the effort necessary for implementation.
** Leads implementation team comprised of engineering resources of his/her organization.
** Commitment: full-time role.
** Current Lead Designers
***
***

* QA Lead (multiple roles)
** Transforms requirements into functionality test plans.
** Develops interface and compliance test procedures according to the architecture.
** Implements black box and white box test tools through the resources of his/her organization.
** Executes test plans and provides test reports.
** Commitment: full-time role.
** Current QA Leads:
***
***

* Release Manager
** Coordinates bug tracking, build and release with the design and QA leads.
** Develops and manages build tools.
** Leads build and release engineering team.
** Commitment: full-time role.
** Current Release Manager: '''[http://meego.com/users/jeremiah Jeremiah Foster (Pelagicore)]'''

* Engineers for Development and QA (many roles)
** Implement and test the required functionality.
** Qualification varies with sub-project.
** Commitment: full-time role.

== Shipping MeeGo IVI Products ==

* [http://news.softpedia.com/news/MeeGo-Powered-In-Vehicle-Information-System-Makes-Appearance-at-MWC-2011-184651.shtml Hawtai B11]
* [http://www.allaboutmeego.com/news/item/12918_Red_Flag_Software_announces_Me.php Geely EC8]
* iKarPC [http://files.icp-deutschland.de/produkte2/124273/web/icp/IKARPC-W08A-datasheet-20110222.pdf datasheet] and [http://www.contradata.it/cataloghi/IEI_2011_In_Vehicle_PC.pdf catalog page]

== MeeGo IVI Demos ==

* MeeGo IVI UI from ICS: [http://www.youtube.com/watch?v=ZWbfGzyLoh8 video] and [http://www.ics.com/services/qtquick info], including source code

== MeeGo IVI UI (HMI)==

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

* [[In-vehicle/IVIHome_Guide | MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide ]]

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2 Contour ShuttleXpress infromation ]

==== Other Scroll Wheels ====
Other scrollwheels that have been used by the MeeGo IVI community

* [[3Dconnexion|3Dconnexion SpaceNavigator ]]

== Roadmap ==

The roadmap is always under discussion. But the important thing it that it is open and transparent - and you can contribute. The path to contribution begins on the MeeGo IVI mailing list. This list is the central communication point with all the MeeGo IVI stakeholders participating. Through this list you can contribute ideas, code, and other resources. You will also receive support and advice as well as pointers to other resources on this list, this is where the community comes together.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found [https://bugs.meego.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MeeGo+IVI+Features&content= here]

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features Submit new MeeGo IVI feature request ]

For a Feature Request to become part of the MeeGo IVI release plan, it needs to clearly define the engineering requirements and have resources working on development.

More details on the long term direction and short term Release plan may be found in the [[In-vehicle/Roadmap|IVI roadmap]].

== Weekly Builds ==
Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.3 Alpha build, '''1.2.90.xx''' is a 1.3 Beta build, '''1.2.99.x''' is a 1.3 Release Candidate.

* [http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the ''images'' link in each weekly build directory. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links under ''repos'' in the weekly build directory.

* [http://repo.meego.com/MeeGo/updates/ MeeGo update repositories ]

==Upcoming Releases==
===Meego 1.2.0 Update ===

;Update release dates
{| border="1"
! Update name
! Code Freeze
! Release
|-
|Update 1
|June 30
|July 15
|-
|Update 2
|August 11
|August 18
|-
|Update 3
|Sept 22
|Sept 29
|}

====Links====
When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:
* [http://repo.meego.com/MeeGo/updates/1.2.0/repos/ MeeGo 1.2.0 Update Repositories]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%2B&known_name=ivibugs_1.2.0Update%2B MeeGo IVI 1.2.0 Update approved bugs ]

* [https://bugs.meego.com/buglist.cgi?emailtype2=substring&field0-0-0=flagtypes.name&classification=MeeGo%20Platform&emailcc2=1&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&email2=ivi-bugs&version=1.2.0&type0-0-0=anywordssubstr&value0-0-0=meego_update_release_blocker%3F&known_name=ivibugs_1.2.0Update%3F MeeGo IVI 1.2.0 Update proposed bugs ]

* [[ Quality/IVI 1.2 Update | IVI 1.2.0 Update bug fix status]]

===Meego 1.3===

;MeeGo 1.3 milestones
{| border="1"
! Milestone
! Date
|-
|New Package Planning complete ||June 30
|-
|Core Package integration ||July 26
|-
|IVI Package integration / version freeze ||August 12
|-
|1.3 branch and Release Candidate 1 ||October 4
|-
|1.3 final release ||October 27
|}

==Platforms==
===MeeGo IVI Platforms Supported in Releases===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! Releases
! Plan
! status
! price/availability
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|1.0.1, 1.1, 1.2
|EOL
|No known driver issues
|unavailable 5/11
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Intel Platform Controller Hub EG20T (Top Cliff)
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, PHUB, CAN
|1.2
|1.3
|No known driver issues
|
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|1.2
|1.3
|[https://bugs.meego.com/buglist.cgi?short_desc=oki&classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&version=1.2&version=1.3&short_desc_type=allwordssubstr&component=Kernel%20and%20drivers%20%28generic%29&product=MeeGo%20IVI CV-ML7213 bugs ]
|
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|ST Microelectronics ConneXt STA2x11
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, '''CAN''', USB-OTG, MSP, BT, FM-Radio
|in development, several issues open, visit [[IVI Images for ConneXt IOH]] for more information
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

===[http://sf2011.meego.com/sites/all/files/slides/meegocon2011developmentboardbofslides.pdf MeeGo IVI Development Boards]===

;IA32
{| border="1"
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! price/availability as of 5/11
! tested with MeeGo?
|-
|Intel Embedded Development Board 1-N450/1-D510
|N450 or D510
|Intel 82801HM
|SSD, WiFi, SATA, USB, SPI, GPIO, PCIe, UART, GigE, Audio, IEGD, DMA, I2C
|[http://edc.intel.com/Platforms/Atom-N450-D410-D510/Development-Board/#bd1-content=bd1-toggle~~visible-content $149 for registered users]
|[http://wiki.meego.com/Devices/Ideapad yes]
|-
|[http://www.exopc.com/devices/ ExoPC]
|Pineview-M N450, 1.66 GHz
|Intel 82801NM
|SSD, WiFi, USB, Mini-HDMI Out, Dock Connector, Bluetooth
|[http://www.exopc.com/devices/where-to-buy/ US$699 ]
|[http://wiki.meego.com/MeeGo_IVI_on_ExoPC yes]
|}

;ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

{| border="1"
! Platform name
! Processor
! GPU; [[ARM/hardfp|hardfp?]]
! Memory
! Features
! price/availability as of 5/11
! tested with MeeGo?
|-
|[http://www.igloocommunity.org/ Snowball] (usable in end products)
|Cortex A-9 Dual-Core Nova A9500 1 GHz
|ARM Mali 400, [http://igloocommunity.org/news/ promised; no GPU support in 6/11 BSP]
|1 GB
|HDMI, WiFi b/g/n, Bluetooth, GPS, USB OTG, FSMC, HSI, Audio, MiPi CSI / Camera, LCD, MiPi DSI, UART, SPI, I2C, GPIO, SD/MMC, accelerometer, magnetometer, gyrometer, pressure sensor [[ARM/Snowball|(complete specs)]]
| [https://shop.strato.com/epages/61428605.sf/en_GB/?ObjectPath=/Shops/61428605/Products/905-00024-B11 160€]
| [[ARM/Snowball|yes]]
|-
|[http://www.igep.es/index.php?option=com_content&view=article&id=46&Itemid=55 IGEPv2]
|[http://www.igep.es/public_docs/IGEPv2/HW_User_Manuals/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf DM3730 1 GHz]
|Imagination Technologies SGX530, yes? (tested by IGES with both TI and Nokia drivers)
|512 MB
|GigE, WiFi b/g, Bluetooth, USB OTG, USB Host, DVI-D, audio, SPI, UART, LCD, serial; [http://shop.igep.es/index.php?main_page=product_info&cPath=1&products_id=49 expansion board] with GSM, VGA, video in, camera, '''CAN'''
| 116.0€ and up plus 152.0€ for expansion board
| yes, but with older Cortex A8 build
|-
|[http://www.variscite.com/products/item/35-var-am35customboard Variscite VAR-AM3517 CustomBoard]
|[http://www.variscite.com/images/stories/DataSheets/VAR-SOM-AM35_1_15.pdf Cortex A-8 Sitara 600 MHz]
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|DMA, QCIF, LCD, SDTV, S-Video, USB, USB OTG, I2C, McSPI, GPIO, MMC, JTAG, '''CAN'''
|$1150 plus shipping
| no
|-
|[http://www.origenboard.org Samsung Origen]
|Samsung Exynos 4210 Cortex A-9 1 GHz
|ARM Mali 400, [http://forums.arm.com/index.php?/topic/14236-mali-gpus-linux-device-drivers-r2p0-05rel0-source-code-released/ reuse Snowball drivers?]
|1 GB
|HMDI, SD, WiFi, Bluetooth, audio, LCD, JTAG, camera
|[http://www.origenboard.org/store.php $199 basic package, "sold out" as of 7/23/2011]
|no
|-
|[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB i.MX53 Quick Start Board]
|Cortex A-8 1 GHz
|Freescale GPUv3, [http://imxcommunity.org/profiles/blogs/ubuntu-rebuilt-with-hardfp yes]
|1 GB
|LVDS, LCD, HDMI, SPDIF, I2C, SSI, SPI, SD/MMC, microSD, SATA, GigE, USB, USB OTG, JTAG, UART, accelerometer
|$149
|[http://www.youtube.com/watch?feature=player_embedded&v=osDlTdl5lAk yes, similar HW]
|-
|[http://pandaboard.org/ Pandaboard]
|Cortex A-9 Dual-Core OMAP 4430 1 GHz
|Imagination Technologies SGX540, [http://article.gmane.org/gmane.comp.embedded.pandaboard/1771/match=hardfp not yet]
|1 GB
|SD/MMC, UART, Camera connector, USB OTG, Audio, GiGE, LCD connector, HDMI, WiFi, Bluetooth, JTAG, SPI, GPIO, I2C, McBSP
|[http://pandaboard.org/content/buy $179]
|[[ARM/OMAP4_Panda|yes]]
|-
|[http://beagle.s3.amazonaws.com/design/xM-A/BB_xM_SRM_A2_01.pdf Beagleboard Xm]
|Cortex A-8 DM3730 1GHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|512 MB
|uSD, USB, USB OTG, UART, McBSP, JTAG, GiGE, Audio, DVI-D, Camera connector, McBSP, I2C, GPIO, MMC2/3, ADC, LCD connector
|[http://beagleboard.org/buy $149]
|[[ARM/Meego_on_Beagleboard_from_scratch|yes]]
|-
|[http://beagleboard.org/static/BBSRM_latest.pdf Beagleboard C4]
|Cortex A-8 OMAP3530 720 MHz
|Imagination Technologies SGX530, [[ARM/Meego_on_Beagleboard_from_scratch|no]]
|256 MB
|I2C, I2S, SPI, MMC, USB, UART, USB OTG, S-Video, Audio, LCD, JTAG, GiGE
|[http://beagleboard.org/buy $125]
|[[ARM/Meego_IVI_on_Beagle|yes]]
|}

=== IVI Ports to Consumer Devices ===

* ia32 Atom processors
** [[MeeGo_IVI_on ExoPC|ExoPC]]

* ARM v7 processors
** [[ARM/TEGRA2|Trimslice Tegra2]]

== Releases ==
* [[MeeGo IVI 1.2 | MeeGo IVI 1.2]]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[Presentations_about_meego-ivi#Presentations_and_Articles_about_MeeGo_IVI|Presentations and articles about meego-ivi]]
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

MeeGo-Lem-Firefox4

2011-08-08T06:12:21Z

Asinnela: Wiki link fixes

=MeeGo-Lem: Installing Fedora Firefox4 from Remi Collet's repository=

With [[MeeGo-Lem|MeeGo-Lem]] installed, additional installations like Firefox 4 become easy. For example,
http://www.if-not-true-then-false.com/2010/install-firefox-4-on-fedora/

==Setup Repos==
Note that instructions for Fedora can't be followed exactly since Fedora uses yum and MeeGo uses zypper. Need to create custom edited zypper repos files:

/etc/zypp/repos.d:
-rw-r--r-- 1 root root 228 2011-04-08 11:13 remi-test.repo
-rw-r--r-- 1 root root 215 2011-04-08 11:13 remi.repo

$ sudo rpm -Uvh http://rpms.famillecollet.com/remi-release-12.rpm
Retrieving http://rpms.famillecollet.com/remi-release-12.rpm
error: Failed dependencies:
fedora-release >= 12 is needed by remi-release-12-6.fc12.remi.noarch
yum is needed by remi-release-12-6.fc12.remi.noarch
$ sudo rpm -Uvh http://rpms.famillecollet.com/remi-release-14.rpm
Retrieving http://rpms.famillecollet.com/remi-release-14.rpm
error: Failed dependencies:
fedora-release >= 14 is needed by remi-release-14-6.fc14.remi.noarch
yum is needed by remi-release-14-6.fc14.remi.noarch
$ sudo rpm --nodeps -Uvh http://rpms.famillecollet.com/remi-release-14.rpm
Retrieving http://rpms.famillecollet.com/remi-release-14.rpm
Failed to expand %__security_plugin macro
Preparing... ########################################### [100%]
1:remi-release ########################################### [100%]
$ sudo rpm -ql remi-release
/etc/apt/gpg/gpg-pubkey-00f97f56-467e318a
/etc/apt/sources.list.d/remi.list
/etc/pki/rpm-gpg/RPM-GPG-KEY-remi
/etc/smart/channels/remi.channel
/etc/yum.repos.d/remi.repo

### Hand edited installed /etc/yum.repos.d/remi.repo to get rid of fedora
### $variables and replace with Specifics....
###
### File '/fedora/1.1.90/remi/mirror' not found on medium 'http://rpms.famillecollet.com/?mediahandler=curl'
### Abort, retry, ignore? [a/r/i/?] (a): a
### Problem accessing the file at the specified URI:
### File '/fedora/1.1.90/remi/mirror' not found on medium
### 'http://rpms.famillecollet.com/?mediahandler=curl'

meegolem-69-~> diff -c /etc/yum.repos.d/remi.repo.~1~ /etc/yum.repos.d/remi.repo
*** /etc/yum.repos.d/remi.repo.~1~ 2010-04-30 23:42:35.000000000 -0700
--- /etc/yum.repos.d/remi.repo 2011-04-08 11:11:56.446387755 -0700
***************
*** 1,16 ****
[remi]
! name=Les RPM de remi pour Fedora $releasever - $basearch
! #baseurl=http://rpms.famillecollet.com/fedora/$releasever/remi/$basearch/
! mirrorlist=http://rpms.famillecollet.com/fedora/$releasever/remi/mirror
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
failovermethod=priority

[remi-test]
! name=Les RPM de remi en test pour Fedora $releasever - $basearch
! #baseurl=http://rpms.famillecollet.com/fedora/$releasever/test/$basearch/
! mirrorlist=http://rpms.famillecollet.com/fedora/$releasever/test/mirror
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
--- 1,16 ----
[remi]
! name=Les RPM de remi pour Fedora 14 - i386
! baseurl=http://rpms.famillecollet.com/fedora/14/remi/i386/
! #mirrorlist=http://rpms.famillecollet.com/fedora/14/remi/mirror
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
failovermethod=priority

[remi-test]
! name=Les RPM de remi en test pour Fedora 14 - i386
! baseurl=http://rpms.famillecollet.com/fedora/14/test/i386/
! #mirrorlist=http://rpms.famillecollet.com/fedora/14/test/mirror
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi

$ sudo zypper ar file:///etc/yum.repos.d/remi.repo
Adding repository 'Les RPM de remi pour Fedora 14 - i386' [done]
Repository 'Les RPM de remi pour Fedora 14 - i386' successfully added
Enabled: Yes
Autorefresh: No
URI: http://rpms.famillecollet.com/fedora/14/remi/i386/

Adding repository 'Les RPM de remi en test pour Fedora 14 - i386' [done]
Repository 'Les RPM de remi en test pour Fedora 14 - i386' successfully added
Enabled: Yes
Autorefresh: No
URI: http://rpms.famillecollet.com/fedora/14/test/i386/

$ sudo zypper clean --all ; sudo zypper --gpg-auto-import-keys refresh
All repositories have been cleaned up.
Retrieving repository 'Adobe Systems Incorporated' metadata [done]
Building repository 'Adobe Systems Incorporated' cache [done]
Retrieving repository 'devel:base (Trunk)' metadata [done]
Building repository 'devel:base (Trunk)' cache [done]
Retrieving repository 'devel:kernel (Trunk)' metadata [done]
Building repository 'devel:kernel (Trunk)' cache [done]
Retrieving repository 'devel:meego-ux (Trunk)' metadata [done]
Building repository 'devel:meego-ux (Trunk)' cache [done]
Retrieving repository 'devel:ux:netbook (Trunk)' metadata [done]
Building repository 'devel:ux:netbook (Trunk)' cache [done]
Retrieving repository 'Fedora 14 - i386' metadata [done]
Building repository 'Fedora 14 - i386' cache [done]
Retrieving repository 'google-chrome' metadata [done]
Building repository 'google-chrome' cache [done]
Retrieving repository 'meego-latest-connectivity' metadata [done]
Building repository 'meego-latest-connectivity' cache [done]
Retrieving repository 'Planet CCRMA 14 - i386' metadata [done]
Building repository 'Planet CCRMA 14 - i386' cache [done]
Retrieving repository 'Fedora Updates at Planet CCRMA 14 - i386' metadata [done]
Building repository 'Fedora Updates at Planet CCRMA 14 - i386' cache [done]
Retrieving repository 'Les RPM de remi pour Fedora 14 - i386' metadata [done]
Building repository 'Les RPM de remi pour Fedora 14 - i386' cache [done]
Retrieving repository 'RPM Fusion for Fedora 14 - Free' metadata [done]
Building repository 'RPM Fusion for Fedora 14 - Free' cache [done]
Retrieving repository 'RPM Fusion for Fedora 14 - Free - Updates' metadata [done]
Building repository 'RPM Fusion for Fedora 14 - Free - Updates' cache [done]
Retrieving repository 'RPM Fusion for Fedora 14 - Nonfree' metadata [done]
Building repository 'RPM Fusion for Fedora 14 - Nonfree' cache [done]
Retrieving repository 'RPM Fusion for Fedora 14 - Nonfree - Updates' metadata [done]
Building repository 'RPM Fusion for Fedora 14 - Nonfree - Updates' cache [done]
Retrieving repository 'Fedora 14 - i386 - Updates' metadata [done]
Building repository 'Fedora 14 - i386 - Updates' cache [done]
All repositories have been refreshed.

$ zypper info firefox
Information for package firefox:

Repository: Les RPM de remi pour Fedora 14 - i386
Name: firefox
Version: 4.0-1.fc14.remi
Arch: i686
Vendor: Remi Collet
Installed: No
Status: not installed
Installed Size: 20.4 MiB
Summary: Mozilla Firefox Web browser
Description:
Mozilla Firefox is an open-source web browser, designed for standards compliance, performance and portability.

== Install Firefox4 from Fedora 14 "remi" repo ==

$ sudo zypper in firefox
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
astronomy-bookmarks firefox xulrunner2

3 new packages to install.
Overall download size: 27.8 MiB. After the operation, additional 49.6 MiB will
be used.
Continue? [y/n/?] (y): y
Retrieving package xulrunner2-2.0-1.fc14.remi.i686 (1/3), 10.6 MiB (29.2 MiB unpacked)
Retrieving: xulrunner2-2.0-1.fc14.remi.i686.rpm [done (583.4 KiB/s)]
Retrieving package astronomy-bookmarks-1-6.fc12.noarch (2/3), 5.0 KiB (5.0 KiB unpacked)
Retrieving: astronomy-bookmarks-1-6.fc12.noarch.rpm [done]
Retrieving package firefox-4.0-1.fc14.remi.i686 (3/3), 17.2 MiB (20.4 MiB unpacked)
Retrieving: firefox-4.0-1.fc14.remi.i686.rpm [done (542.8 KiB/s)]
Installing: xulrunner2-2.0-1.fc14.remi [done]
Installing: astronomy-bookmarks-1-6.fc12 [done]
Installing: firefox-4.0-1.fc14.remi [done]
Additional rpm output:

WARNING : This firefox 4.0 RPM is not an official
Fedora build and it overrides the official one. Don't file bugs on Fedora Project.

Use dedicated forums http://forums.famillecollet.com/

$ rpm -ql astronomy-bookmarks
/usr/share/bookmarks
/usr/share/bookmarks/default-bookmarks.html

The result (after a little customization to get rid of traditional menubar):

[[File:Meegolem-firefox4.png]]

==Force Firefox4 as default browser==

If the following isn't done, unless the browser is pre-started, bad stuff happens when clicking
links in twitter/facebook on homepanel. After these are set, Firefox4 is brought up on clicking URL.

$ xdg-settings get default-web-browser
google-chrome.desktop
$ xdg-settings set default-web-browser mozilla-firefox.desktop
$ xdg-settings get default-web-browser
mozilla-firefox.desktop

For those that only want Firefox4 installed, some of the "bad stuff" can be prevented by removing package 'chromium' and replacing /usr/bin/chromium-browser with the following script, since calls to /usr/bin/chromium-browser appear hard-wired from the MeeGo Netbook UX panel.

#!/bin/sh
exec firefox $*

==Install nspluginswrapper to enable embedded gecko media player playback==

Note that in order to get media to play in the installed browser, per [[MeeGo-Lem#Be_able_to_watch.2Fhear_common_internet_media_formats]], Fedora 14's nspluginwrapper also needs to be installed. Without it, the plugin "mplayerplug-in is now gecko-mediaplayer 1.0.0"
doesn't play back mp3, AVI, or other common internet media:

$ zypper in nspluginwrapper
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
nspluginwrapper

1 new package to install.
Overall download size: 144.0 KiB. After the operation, additional 431.0 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package nspluginwrapper-1.3.0-14.fc14.i686 (1/1), 144.0 KiB (431.0 KiB unpacked)
Retrieving: nspluginwrapper-1.3.0-14.fc14.i686.rpm [done]
Installing: nspluginwrapper-1.3.0-14.fc14 [done]

==Install Grab-and-Drag for Touch Screen Support==

Using Firefox->Add-ons...->Extensions, search for [http://grabanddrag.mozdev.org/index.html "grab and drag"] and
install.... with a few customizations, it works nicely on Lenovo S10-3t touchscreen. Be sure to configure the options:

[[File:Meegolem-firefox4-grab-and-drag-prefs.png]]

==Setup Firefox4-based BlueGriffon Web Editor Too==

Remi Collet's Fedora repository is an [http://bluegriffon.org/pages/Download official distribution point] for the http://BlueGriffon.org web editor: "BlueGriffon is a new WYSIWYG content editor for the World Wide Web. Powered by Gecko, the rendering engine of Firefox 4, it's a modern and robust solution to edit Web pages in conformance to the latest Web Standards.... Because Gecko lives inside BlueGriffon, the document you edit will look exactly the same in Firefox 4."

Setting up MeeGo's repositories for Firefox4 also allows Bluegriffon to be installed with ease:

$ zypper se griffon
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
--+-------------+--------------------------------------+--------
| bluegriffon | La nouvelle génération d'éditeur web | package

$ sudo zypper in bluegriffon
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by bluegriffon-1.0-4.fc14.remi.i686
Solution 1: do not install bluegriffon-1.0-4.fc14.remi.i686
Solution 2: break bluegriffon by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following NEW package is going to be installed:
bluegriffon

1 new package to install.
Overall download size: 15.1 MiB. After the operation, additional 40.4 MiB will
be used.
Continue? [y/n/?] (y): y
Retrieving package bluegriffon-1.0-4.fc14.remi.i686 (1/1), 15.1 MiB (40.4 MiB unpacked)
Retrieving: bluegriffon-1.0-4.fc14.remi.i686.rpm [done (530.5 KiB/s)]
Installing: bluegriffon-1.0-4.fc14.remi [done]

$ bluegriffon &
/usr/lib/bluegriffon/bluegriffon-bin: /usr/lib/libjpeg.so.62: no version information available (required by /usr/lib/bluegriffon/libxul.so)
[1] bluegriffon &

The result, showing Bluegriffon editing http://meego.com :

[[File:bluegriffon-web-editor-on-meegolem.png]]

==Upgrading To New Versions of Firefox==

With Remi Collet's respository setup, 'zypper up' will also upgrade to the lastest versions. For example the bugfix release Firefox 4.01 was released recently, and the upgrade was easy:

$ zypper up firefox
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides libjpeg.so.62(LIBJPEG_6.2) needed by xulrunner2-2.0.1-
1.fc14.remi.i686
Solution 1: do not install firefox-4.0.1-1.fc14.remi.i686
Solution 2: break xulrunner2 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following packages are going to be upgraded:
firefox xulrunner2

2 packages to upgrade.
Overall download size: 27.7 MiB. After the operation, 46.0 KiB will be freed.
Continue? [y/n/?] (y): y
Retrieving package xulrunner2-2.0.1-1.fc14.remi.i686 (1/2), 10.5 MiB (29.2 MiB unpacked)
Retrieving: xulrunner2-2.0.1-1.fc14.remi.i686.rpm [done (46.7 KiB/s)]
Installing: xulrunner2-2.0.1-1.fc14.remi [done]
Installing: firefox-4.0.1-1.fc14.remi [done]
Additional rpm output:

WARNING : This firefox 4.0.1 RPM is not an official
Fedora build and it overrides the official one. Don't file bugs on Fedora Project.

Use dedicated forums http://forums.famillecollet.com/

OBS

2011-08-08T06:08:35Z

Asinnela: Wiki link fix

'''Open Build Service (OBS)'''

The OBS (Open Build Service) is a build management system written for the community by openSuse/Novell.

MeeGo has two main OBS setups:
* The [[Core OBS]] : https://build.meego.com/ - used by core developers to build the main MeeGo distribution; accounts provided to anyone who earns commit rights to a MeeGo package. More information on how to get an account can be found [[Build_Infrastructure/Packagers_Developers#How_to_get_started|here]]
* The [[OBS/Community OBS|Community OBS]] : https://build.pub.meego.com/ - used by MeeGo community members to build opensource applications and libraries

Additionally vendors may have private OBS installations

OBS installations may be linked to each other so that software build on a vendor OBS or the community OBS may refer to and track software packages being developed on the core OBS.

Whilst the OBS does the bulk of the compiling and building there is additional QA, automation and test infrastructure used by the MeeGo Project : The [[Build Infrastructure]] article has more details.

'''OBS Documentation'''

* Documentation root: [[Build Infrastructure/Packagers Developers]]
* OSC tutorial: [[Build Infrastructure/Packagers Developers/CLI Part 1]]
* [[Getting_started_with_OBS|OBS Getting started guide]]

'''Get a Community OBS account'''

https://build.pub.meego.com/user/register_user

'''Setup a local test instance'''

There is a wiki article on how to [[OBS setup|setup a Build Service of your own]] - note that you don't need to do this to build locally; it's only usually needed by vendors.

Quality/Getting started

2011-08-08T04:45:36Z

Asinnela: Fixing wiki links

= Getting started with contributing to MeeGo QA =

There are a lot of ways for you to become part of MeeGo quality team, no matter you are technical person or not.

* '''Try our daily build'''
** MeeGo release engineers are producing in-development daily builds, which are available [http://repo.meego.com/MeeGo/snapshots/stable/ HERE]. By trying these builds, you will get the opportunity to enjoy latest fancy features, although you will also get chance to spot new issues as a side effect. Daily builds are not targeted for everyone, as many features may not be fully functional and regressions may happen, but your feedback for them would be very helpful to improve the quality of our releases. If it sounds too scary for you to try daily builds, you could pick up our [http://repo.meego.com/MeeGo/releases/ stable releases] by providing same types of feedback.
** You could feedback to us by reporting bugs @ https://bugs.meego.com, or sending emails to [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list].

* '''Help out one of our [[Quality#Projects|quality teams for projects]]'''
** If you have special interest or expertise in one of our projects, you are welcomed to help corresponding quality team to contribute in executing existing test cases, developing new test cases, reporting and following up bugs etc.

* '''Participate in QA tools development activities'''
** MeeGo QA tools team is developing and maintaining a bunch of [[Quality/QA-tools|tools for quality assurance]]. You are welcomed to contribute in [[Quality/QA_tools_development|QA tools development activities]].

* '''Contribute in sys-debug activities to root cause bugs and assign them to right package'''
** sys-debug activities are meaningful in facilitating bug fixes since a number of bugs especially system level bugs could be fixed more efficiently if they could be analyzed first to decide the guilty package so that right owner could be assigned the bug and work on it. The details of sys-debug process has been defined [[Quality/SysDebug|here]].

Quality

2011-08-08T04:40:53Z

Asinnela: Fixing wiki links

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [[Quality/Getting started|How Can I Contribute]]
== Projects ==

For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com]

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [[Quality/Plans/1_2_Handset_UX_test_plan|MeeGo HandSet UX Test Plan]]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [[Quality/1.2NetbookTestPlan|1.2 SW Update Test Plan]]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Find our tools and contact information]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/triageteam_assignee | Process to deal with bugs assigned to triageteam@meego.bugs]]
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]
* [[/error_manager | MeeGo Error Managers]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

== Meetings ==

General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]]

QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]]
** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo.

== Questions and Answers ==

* What is the QA contact expected to do actually?
** QA contact work with/support/advice/help package maintainers (see [http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility|Fedora example] or [[Packaging/Guidelines#Maintaining_a_Package|MeeGo guidelines for maintaining package]]) and other users on QA related issues/questions for component in case.
*** Features ("Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases." from [[https://meego.com/developers/requirements ]])
**** make testability analysis for features (yes or no value to testability field) and
**** identify "feature acceptance tests" together with product management and package maintainers that could be used at the end as a criteria for feature status to be changed as "VERIFIED".
*** Bugs ("QA Contact or Bug Submitter verifies bug fixing with the "how to re-produce" instructions in the original bug report when the bug is marked as RELEASED - FIXED." from [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling page]])
**** facilitate the whole bug life-cycle from QA perspective, including ensure bug report completeness, follow up bugs by providing helpful or required information in timely fashion to accelerate bug fixing and verify the issue after fix is integrated, especially when the original reporter is not responsive or has difficulty to follow the bug up.
**** actively follow-up the bugs. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible.

[[Category:QA]]

Getting started with Harmattan Python

2011-06-23T11:11:28Z

Asinnela: Redirected page to Python/Harmattan/Getting started

#REDIRECT [[Python/Harmattan/Getting started]]

ARM/N900/CommunityEdition

2011-06-23T11:11:00Z

Asinnela: Redirected page to ARM/N900

#REDIRECT [[ARM/N900]]

Quality/QA-tools/User experience

2011-06-23T09:24:56Z

Asinnela: /* Ongoing Work */

= MeeGo QA tools user experience =

This is the main page for user experience (UX) work done for MeeGo QA tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-users and their input are crucial. By understanding the users and their needs, it is possible to develop something that really benefits the users.

This page is meant for giving an overview of UX activities regarding QA tools. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla.

== UX Workflow in a Nutshell==

User experience is not something that could just be added to a product as the last thing of the implementation process. On the contrary, user experience work focuses on taking the users into account in every phase of the development process. The following gives just one example on how you can do user-centered design in practice:

# Identify who are the actual and/or potential users
# Conduct a user study and identify the users' needs and wishes
# Draft and iterate e.g. a paper prototype of the planned UI with the users
# Based on the iterated prototype and other input, design and implement a functional prototype
# Present the functional prototype to the users as early as possible and gather feedback and improvement ideas. You can also conduct a more formal usability study.
# Re-design and continue implementation
# Once the first complete version is released, continue to gather user feedback and implement improvements

Meeting users face-to-face is preferred but online methods can also be used. E.g. the input can be gathered via mailing lists or IRC, and design drafts can be published to wiki or Bugzilla.

== Ongoing Work==

Please add information here if you are doing something regarding improving UX of QA tools.

== Proposal for Future Work ==

* Every Tool
** Evaluate the ease of the installation and the first time use
** Improve visual look of the GUI tools, e.g. improve icons and other graphical elements
* MeeGo N900 DE
** UX evaluation / study
** [[ARM/N900/TabletUX]]

== How to Participate ==

The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are:
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net] for discussing about the tools and QA processes in general
* [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Bugzilla] for reporting enhancement ideas or usability problems

Quality/QA tools development

2011-06-07T15:31:10Z

Asinnela: /* Documentation */

= QA tools development =

This page provides information on the development activities and practices of QA tools. The focus is on presenting things that are relevant for people interested in developing the tools. The main page for the end users is [[Quality/QA-tools|here]].

Anyone is welcome to contribute and non-member contributions will be treated with same process and review as member contributions. We follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://meego.gitorious.org/meego-quality-assurance/ git repositories] and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.

'''Targets:'''

* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance
* Improve MeeGo test automation (execution and software installation) - target from MeeGo release engineering

"As Core OS release release manager I want to verify trunk:testing packages frequently so that I know the quality of nightly/weekly releases."

== Tools and Maintainers ==

Tool maintainers are selected based on developer experience with particular tool/package or seniority. Tool maintainers have been agreed [[Quality/QA-tools/Meetings|in the QA-tools meeting]] Tuesday September 7th 2010. Changes, if needed, are discussed also there.

In practice only tool maintainers will have commit and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Others must follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines] to submit patches or personal clone + merge request approach.

The maintainer of the tree shall update the changelog.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Gitorious'''||'''Maintainer''' ||'''Substitute'''
|-
| [[Quality/QA-tools/Test-definition|test-definition]]||[http://meego.gitorious.org/meego-quality-assurance/test-definition Gitorious] || Sampo Saaristo || Timo Härkönen
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||[http://meego.gitorious.org/meego-quality-assurance/testrunner-lite Gitorious] || Sampo Saaristo || Kyösti Ranto
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || [http://meego.gitorious.org/meego-quality-assurance/testrunner Gitorious] || Kyösti Ranto || Timo Härkönen
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] ||[http://meego.gitorious.org/meego-quality-assurance/testplanner Gitorious] || Kyösti Ranto || N/A
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] ||[http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing Gitorious] || Timo Härkönen || Timo Mäkimattila
|-
| [[Quality/QA-tools/OTS|OTS - Open Test System]] ||[http://meego.gitorious.org/meego-quality-assurance/ots Gitorious] || Elias Luttinen || Ville Niutanen
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||[http://gitorious.org/qa-tools/meego-ai Gitorious] || Timo Härkönen || N/A
|-
| [[Quality/TestSuite/MCTS|MeeGo Core Test Suite]] || [http://meego.gitorious.org/meego-quality-assurance/mcts/ Gitorious] ||Matti Salmi || Jeff Zheng
|-
| [[Quality/Netbook Test Suite and Utilities|MeeGo Netbook Test Suite]] || [http://gitorious.org/qa-tools/mnts/ Gitorious] ||Jeff Zheng || N/A
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || [http://gitorious.org/qa-tools/qtuitest-mbt-adapter Gitorious] || Riku Halonen || N/A
|-
| [http://min.sourceforge.net/ MIN test framework] || [http://meego.gitorious.org/meego-quality-assurance/min Gitorious] || Sampo Saaristo || Timo Mäkimattila
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || [http://gitorious.org/TDriver Gitorious] || Petri Kiiskinen || Tatu Lahtela
|-
| Rich Core dumper || [http://meego.gitorious.org/meego-quality-assurance/rich-core Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter settings || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter-settings-public Gitorious] || Carol Rus || Raimo Gratseff
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] || [http://meego.gitorious.org/meego-quality-assurance/hat-control Gitorious] || Marko Junttila || Riku Halonen
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || [http://meego.gitorious.org/meego-quality-assurance/qa-reports Gitorious] || Sami Hangaslammi || Jarno Keskikangas
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || [http://meego.gitorious.com/meego-quality-assurance/scripts-and-utils Gitorious] || N/A || N/A
|-
| [[Quality/TestSuite/handset-test-suite/handset-ux-test_Releases | handset_ux_tests]] || [http://meego.gitorious.com/meego-quality-assurance/handset-ux-tests Gitorious] || JessicaJi || N/A
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] || [http://meego.gitorious.org/meego-quality-assurance/meego-testing-hudson-plugin Gitorious] || Alexey Kuznetsov || Timo Härkönen
|-
| Service OS based Flasher || [http://meego.gitorious.org/meego-quality-assurance/meego-ai-serviceos Gitorious] || Jing Wang || N/A
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] || [http://meego.gitorious.org/meego-quality-assurance/libcqpid Gitorious] || Sami Lahtinen || N/A
|}

If you are interested in the user experience work regarding these tools, you can find more information [[Quality/QA-tools/User experience|here]].

=== Overview ===

The figure below tries to summarize the relations and tasks of the tools when used in test automation context.

[[File:testautomationtools.png]]

xfig file:[[File:qatools.fig]]

== Release Practices ==

Here is the workflow for QA tools release practices.

{| border="1" cellspacing="0"
|+
|'''Role'''
|'''Description'''
|-
| Developer || Anyone who wants to participate in qa-tools development
|-
| VCS Maintainer || Component owner who has commit rights in version control system (VCS)
|-
| Package Maintainer || Integrator whose responsibility is the OBS packaging
|-
| Release Management || Third party who is responsible of trunk:testing releases(?)
|}

[[File:Release.png]]

Kivio file: [[File:Release.flw]]

# Developer creates merge request(s) in gitorious.
# VCS Maintainer tests and accepts merge requests.
# VCS Maintainer checks/updates change logs.
# VCS Maintainer tags a version.
# VCS maintainer sends email to [http://lists.meego.com/pipermail/meego-qa/ meego-qa mailing list] based on the following template
Topic: Integration request: package-name version
PACKAGE: package-name
TAG: tag name
URL: link to sources
CHANGES: short description of changes containing bugs.meego.com bug numbers of fixed bugs
# Package maintainer updates the OBS package.
# Package maintainer tests the OBS package.
# If the package belongs to tools:testing and passes testing, Package Maintainer may accept it. If the package belongs to trunk:testing, Package Maintainer creates a promotional request to Release Management. (If the package belongs to both repositories, we let the Release Management set bugs fixed by the package to RELEASED state).
# Host side tools are updated to tools:testing after verifying functionality
# Package maintainer replies to meego-qa list about the actions done with the updated package. e.g. 'Updated in devel:quality and sent promotion request to testing'
# Release Management accepts the package. Or not. (Follow meego-packaging and meego-commits.)

''' YouTube videos '''

YouTube is a good way to communicate new features. You can find existing demo videos on [http://www.youtube.com/user/meegoqatools meegoqatools channel on Youtube].

If you shoot a video to YouTube, promote it on meego-qa mailing list!

You can find some hints how to shoot, edit, and upload a video here: [[YouTube_Hints]]

=== Release checklist ===
To make sure fixes are released without delay, check that the following conditions are met

# Change logs are updated and contain relevant references to MeeGo bugzilla
# Created obs request include fixes bug numbers from MeeGo bugzilla
# Bugzilla items listed in changes are set as resolved
# Spec file matches [[Packaging/Guidelines|MeeGo packaging guidelines]]
# Rpmlint warnings are either fixed or explained by comments in the spec file. e.g. eat packages install files into root's home and the reasoning for it needs to be explained
# Host side tool packages use the same source tar ball to produce debian and rpm packages

== Roadmap ==

These are the items that we're currently working on.

The features in the roadmap are followed with META FEA bugs. The features are split to small tool specific FEA:s that block the feature META bug. The META bug is then the last bug to be closed when the feature is finished. You can also follow the tool bug progression from the dependency trees of the META bugs.

Adding a new feature to the roadmap:
# Add a feature bug describing the main purpose of the feature with META and FEA tags.
# Add separate bugs for each tool specific change
# Add correct dependencies between tool specific bugs (e.g. testrunner bug depends on testrunner-lite bug that depends on test-definition bug...)
# Make all of the bugs block the META bug

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12980&hide_resolved=0 Measurement support]
|-
| [[Quality/QA-tools/OTS/Roadmap|OTS releases]]
|}

== Future development ==

The focus is currently on [[ARM/N900/QA|N900 Developer Edition QA]]. Hence the N900 related list below doesn't have a comprehensive information about target builds or priorities. The items listed here are not currently worked on but are planned to be implemented in the long run.

A list of defined features:

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/show_bug.cgi?id=12810 Easy install]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12454&hide_resolved=0 Parallel testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12981&hide_resolved=0 Events feature in automatic testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12937&hide_resolved=0 MCTS coverage support]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12833&hide_resolved=0 Test environment validation]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=13092&hide_resolved=0 Test equipment control]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12971&hide_resolved=0 Qt Creator integration]
|-
| [https://bugs.meego.com/show_bug.cgi?id=13190 A tool that combines Testrunner and Testplanner]
|}

== Design/ Planning ==

* [[Quality/QA-tools/MCTS test automation design|MCTS Test Automation]] (QA Tools support for MCTS)

== Documentation ==

Please make sure that all the relevant documentation regarding the tools is kept up-to-date whenever you update any of the tools. Please consider the end users of the tool as the primary readers of the documentation and make the documentation task-oriented for end user needs. Separate developer documentation can exist as well.

'''Wiki guidelines'''

Every tool should have a wiki page that contains at least 1) Overview of the tool and its benefits 2) Installation instructions 3) Basic use tutorial 4) Contact information.

Make sure that you are familiar with [[Wiki contribution guidelines|MeeGo wiki contribution guidelines]] before creating new content. Currently, there are quite a lot problems relating to e.g. page names, wiki links, deep hierarchies and obsolete pages in our wiki section.

'''Documentation checklist'''

The following table lists the tool-specific documentation that should exist (marked with 'x'). These should be checked frequently and more in depth in the future. Bugs will be filed for the missing or inaccurate documentation (marked as 'NOK' i.e. "Not OK").

{| border="1" cellspacing="0"
|+
|'''Tool''' ||'''Doxygen'''||'''Help''' ||'''Man pages''' || '''Wiki'''
|-
| test-definition || || || || x Checked: asinnela 2011-03-03
|-
| testrunner-lite || x || x Checked: asinnela 2011-03-07 || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14074 Bug 14074] || x Checked: asinnela 2011-06-07
|-
| Testrunner || x || x Checked: asinnela 2011-03-07 || || x Checked: asinnela 2011-03-07
|-
| Testplanner || x || x Checked: asinnela 2011-03-10 || || x Checked: asinnela 2011-03-07
|-
| eat - enables automated testing || || || || x Checked: asinnela 2011-03-08
|-
| OTS - Open Test System || x || x || x || x Checked: asinnela 2011-03-25
|-
| MIN test framework || x || x || x ||
|-
| Scripts and utils || || || || x Checked: asinnela 2011-03-11
|-
| MeeGo Fast Feedback Testing || x || x || || x Checked: asinnela 2011-03-11
|-
| Qpid C wrapper library - libcqpid || x || || || x Page created, content to be added.
|}

'''Other documentation'''

* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]
* [[Quality/QA-tools/How_to_set_up_repositories|How to set up the repositories that are needed to install QA tools]]

== Meetings ==

All meetings will be held in <code>#meego-meeting</code> on <code>irc.freenode.net</code>.

* Team meetings
** QA-tools weekly meetings are held on every Tuesday 08:00 UTC in #meego-meeting2 on irc.freenode.net (please note the "2") from May 3rd 2011 onwards.
** [[Quality/QA-tools/Meetings|Meeting agendas and minutes]]

* Architecture meetings
** Architecture meetings will be held on-demand basis.
** [[Quality/QA-tools/Arch-Meetings|Meeting agendas and minutes]]

* Workshops
** Face-2-face meetings within the team.
** [[Quality/QA-tools/Workshops|Meeting agendas and minutes]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
** Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
** [http://timoph.fi/qa-tools-stats/ Old #meego-qa-tools statistics]
** [http://timoph.fi/qa-tools-logs-archive/ Archived #meego-qa-tools logs]
* Gitorious team, http://meego.gitorious.org/meego-quality-assurance/
* [http://www.youtube.com/user/meegoqatools Youtube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]
* MeeGo OBS - devel:quality
* This wiki area
* [[Quality/QA-tools/ServiceOS|ServiceOS]]
* [[Quality/QA-tools/PXEInstall|PXEInstallation]]

== Team members ==

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
| '''Name'''
| '''Role'''
| '''Affiliation'''
| '''IRC nickname'''
|-
| Riku Halonen || Team member || Nokia || rikhalon
|-
| Kari Sievi || Team member || Digia || sievi
|-
| Timo Härkönen || Team member || Digia || timoph
|-
| Carol Rus || Team member || Digia || carrus
|-
| Sami Lahtinen || Team member || Digia || slahtinen
|-
| Raimo Gratseff || Team member || Digia || rrraimo
|-
| Kyösti Ranto || Team member || Digia || kyranto
|-
| Joonas Kylänpää || Team member || Digia || Kaadlajk
|-
| Timo Mäkimattila || Team member || Digia || timakima
|-
| Elias Luttinen || Team member || Digia || eluttine
|-
| Ville Niutanen || Team member || Digia || Villen
|-
| Vesa Poikajärvi || Team member || Digia || vesse
|-
| Alexey Kuznetsov || Team member || Digia || alkuznet
|-
| Daniil Chuiko || Team member || Digia || dachuiko
|-
| Jarmo Savinen || Team member || Digia || jasavi
|-
| Sampo Saaristo || Team member || Sofica || sampos
|-
| Ling Yu || Team member || Intel || -
|-
| Jing Wang || Team member || Intel || -
|-
| Tuomo Mäkinen || Team member || Ixonos || -
|-
| Jouni Leppäkases || Team member || Ixonos || jouni
|-
| Jarno Keskikangas || Team member || Leonidas || jakeskik
|-
| Janne Hietamäki || Team member || Leonidas || _janne
|-
| Sami Hangaslammi || Team member || Leonidas || sahangas
|-
|}

 
[[Category:QA]]

N900de

2011-05-27T06:07:47Z

Asinnela: Redirected page to ARM/N900

#REDIRECT [[ARM/N900]]

N900DE

2011-05-27T06:07:34Z

Asinnela: Redirected page to ARM/N900

#REDIRECT [[ARM/N900]]

ARM/N900/DeveloperEdition.

2011-05-27T06:07:21Z

Asinnela: Redirected page to ARM/N900

#REDIRECT [[ARM/N900]]

ARM/N900/HE

2011-05-27T06:07:00Z

Asinnela: Redirected page to ARM/N900

#REDIRECT [[ARM/N900]]

Quality/Meetings

2011-05-17T10:12:46Z

Asinnela: /* Logs */

== Logistics ==

Until further notice, the MeeGo QA meets every Tuesday at 07:00 UTC for one hour.
All MeeGo QA meetings take place in the MeeGo IRC channels:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-qa
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18h before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==
'''Tuesday May 7th 2011 07:00 UTC''' - Agenda Proposal

This meeting is focusing different process and procedure related items. If time we will also have short period for questions to QA Leads. Please anyhow remember to update your verticals QA status.

* Opening and general news
* Actions from previous meetings (2011-05-10)
* Creating "release" for tests working with release 1.2?
** Shall we have test suites branched with the release? Answer: Yes.
** Need to make a "release" out from that and make sure that tests are working -> file bugs and create xml-files if need to be
* Unify "test type" name on qa-reports.meego.com - follow-up
* Update to 1.2 QA Situation (QA Leads and QA-tools)
** Leads create short summary to Wiki min 1h prior the meeting so that in the meeting we can concentrate on questions and discussion
** [[Quality/Meetings/QA leads update 1.2| Weekly Updates from QA Leads]]

== Logs ==
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-17-07.00.html 2011-05-17 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-10-06.59.html 2011-05-10 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-03-07.00.html 2011-05-03 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-04-26-06.59.html 2011-04-26 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-19-07.00.html 2011-04-19 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-07.01.html 2011-04-12 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-07.06.html 2011-03-29 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-22-07.08.html 2011-03-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-06.59.html 2011-03-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-01-06.59.html 2011-03-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-22-07.00.html 2011-02-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-15-07.00.html 2011-02-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-08-07.00.html 2011-02-08 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-01-06.59.html 2011-02-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-25-07.01.html 2011-01-25 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-06.59.html 2011-01-18 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-06.59.html 2011-01-11 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-04-07.00.html 2011-01-04 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-28-07.00.html 2010-12-28 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-21-07.02.html 2010-12-21 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-14-07.01.html 2010-12-14 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-06.59.html 2010-12-07 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-06.59.html 2010-11-30 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-06.59.html 2010-11-23 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html 2010-11-09 Meeting minutes]

== Materials used in meetings - if not anyplace else ==
* [[Quality/Meetings/QA nominations 101201| QA Nomination proposals for 1st of Dec 2010 TSG Meeting]]
* [[File:QAtoolproposal.pdf]] - proposal about new QA tool discussed on Dublin QA Workshop (un-conference day)

Quality/QA-tools

2011-05-11T11:00:18Z

Asinnela: /* Tools, test suites and other utilities */ This section doesn't contain test suites anymore

= Quality assurance (QA) tools =

''' We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there. '''

[[File:Tool_meegon.png|400px]]

Quality Assurance tools are developed to ensure MeeGo SW quality. QA tools team develops and maintains tools for quality assurance.

* "Open source tools – available for all, available for development and contributions. Make people accountable for quality."

'''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|QA tools development]] page. We apologize for any inconvenience. The target is to make this page clearer and more informative for the actual users of QA tools.

== Overview ==

QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the figure below. In addition, there are also a couple of concept videos available at our [http://www.youtube.com/user/meegoqatools YouTube channel]:
* [http://www.youtube.com/watch?v=WdXBqGdLz8I Tool offering for manual testing]
* [http://youtu.be/Ry4MM-CX2b8 Test automation]

[[File:Meego-qa-tools.png|600px]]

== Tools and other utilities ==

If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]].

'''Test tools'''

Each wiki page will contain more detailed description, installation instructions and tutorial on the basic usage. For now, please [[Quality/QA-tools#Collaboration spaces|contact us]] if you need help. Currently, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, Meego-ai, libcqpid, eat and MIN from Tools:Testing repository. The instructions for setting up the repositories can be found [[Quality/QA-tools/How_to_set_up_repositories|here]].

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device tool for sending core dumps to core dump data base
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|-
| [[Quality/QA-tools/CrashReports|Crash Reports]] || Reporting tool for automatic crash reports
|-
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance
|}

'''Other utilities'''

{| border="1" cellspacing="0"
|+
|'''Name (link to wiki page)''' ||'''Short description'''
|-
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||
|-
| Rich Core dumper ||
|-
| Crash Reporter settings || Settings package for Crash Reporter
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] ||
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] ||
|-
| Service OS based Flasher ||
|}

'''Tools and utils not in active development'''

Tools listed here are in maintenance and no new features are planned to be implemented in the near future to them.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || Test execution tool with graphical UI
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] || Simple tool for creating and editing test plan files
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] ||
|-
| [http://min.sf.net/ MIN Test Framework] || Advanced test framework
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] ||
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] ||
|}

== Feature requests and bugs ==

Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=ASSIGNED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance Assigned bugs and features - Working on it]
* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order]

Bugzilla instructions:
* [[Quality/How To Report Bugs|How to report bugs]]
* [[Quality/Bug Life Cycle and Handling|Bugzilla workflow]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
* [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]

== Nice to have ==

None of the existing tools answer your needs? Here is where you should enter any suggestion.

* Relieve localization testing effort by automating all or part of it (suggested by: helia_co, detail to be added).

 
[[Category:QA]]

Quality/QA-tools/Meetings

2011-04-27T19:30:29Z

Asinnela: /* QA Tools - Weekly Meetings */

= QA Tools - Weekly Meetings =

QA-tools weekly meetings are held on every Tuesday 08:00 UTC in <code>#meego-meeting2 on irc.freenode.net</code> (please note the "2") from May 3rd 2011 onwards.

== Next meeting ==

'''Tuesday May 3rd 2011 08:00 UTC''' - Agenda Proposal

* Restructure QA tool page
* Latest Tool Status
* QA tools status update
* Any Other Business

== Previous Meeting Minutes ==

'''Tuesday December 7th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-11.59.html Minutes of the meeting]

'''Tuesday November 30rd 2010 12:00 UTC'''

* Regular Meeting Agenda
* Discussion on test report templates support at qa-reports.meego.com (#9922)

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-11.59.html Minutes of the meeting]

'''Tuesday November 23rd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-11.59.html Minutes of the meeting]

'''Tuesday November 16th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-16-11.59.html Minutes of the meeting]

'''Tuesday November 9th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-11.59.html Minutes of the meeting]

'''Tuesday November 2nd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-02-12.06.html Minutes of the meeting]

'''Tuesday October 26th 2010 12:00 UTC'''

* Regular Meeting Agenda
* Co-maintainer for Tools:Testing

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-26-12.00.html Minutes of the meeting]

'''Tuesday October 19th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-19-12.00.html Minutes of the meeting]

'''Tuesday October 12th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-12-11.57.html Minutes of the meeting]

'''Tuesday October 5th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-05-11.57.html Minutes of the meeting]

'''Tuesday September 28th 2010 12:00 UTC'''

* Action points from last meeting
* Released packages and videos
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-28-11.57.html Minutes of the meeting]

'''Tuesday September 21th 2010 12:00 UTC'''

* Action points from last meeting
* OTS client toolchain status
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-21-11.57.html Minutes of the meeting]

'''Tuesday September 14th 2010 12:00 UTC'''

* Action points from last meeting
* Review of Release Practices proposal (Timo Härkönen & Timo Mäkimattila)
* Status check of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-14-11.57.html Minutes of the meeting]

'''Tuesday September 7th 2010 12:00 UTC'''

* Tool maintainers and substitutes
* Release practices
* Status check of bugs and development

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-07-11.57.html Minutes of the meeting]

'''Tuesday August 31th 2010 12:00 UTC'''

* Short intro for project targets and tools we work with
* Status of open bugs / features at [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=eat&component=min&component=testdefinition&component=testrunner-lite&product=Development%20Tools bugs.meego.com]
* Review of released demo videos
* Review of contribution guidelines

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-31-11.57.html Minutes of the meeting]

Quality/QA-tools/Meetings

2011-04-27T17:34:36Z

Asinnela: Reformatted the bullets

= QA Tools - Weekly Meetings =

QA-tools weekly meetings are held every on Tuesday 08:00 UTC in <code>#meego-meeting2 on irc.freenode.net</code> (please note the "2") from May 3rd 2011 onwards.

== Next meeting ==

'''Tuesday May 3rd 2011 08:00 UTC''' - Agenda Proposal

* Restructure QA tool page
* Latest Tool Status
* QA tools status update
* Any Other Business

== Previous Meeting Minutes ==

'''Tuesday December 7th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-11.59.html Minutes of the meeting]

'''Tuesday November 30rd 2010 12:00 UTC'''

* Regular Meeting Agenda
* Discussion on test report templates support at qa-reports.meego.com (#9922)

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-11.59.html Minutes of the meeting]

'''Tuesday November 23rd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-11.59.html Minutes of the meeting]

'''Tuesday November 16th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-16-11.59.html Minutes of the meeting]

'''Tuesday November 9th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-11.59.html Minutes of the meeting]

'''Tuesday November 2nd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-02-12.06.html Minutes of the meeting]

'''Tuesday October 26th 2010 12:00 UTC'''

* Regular Meeting Agenda
* Co-maintainer for Tools:Testing

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-26-12.00.html Minutes of the meeting]

'''Tuesday October 19th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-19-12.00.html Minutes of the meeting]

'''Tuesday October 12th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-12-11.57.html Minutes of the meeting]

'''Tuesday October 5th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-05-11.57.html Minutes of the meeting]

'''Tuesday September 28th 2010 12:00 UTC'''

* Action points from last meeting
* Released packages and videos
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-28-11.57.html Minutes of the meeting]

'''Tuesday September 21th 2010 12:00 UTC'''

* Action points from last meeting
* OTS client toolchain status
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-21-11.57.html Minutes of the meeting]

'''Tuesday September 14th 2010 12:00 UTC'''

* Action points from last meeting
* Review of Release Practices proposal (Timo Härkönen & Timo Mäkimattila)
* Status check of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-14-11.57.html Minutes of the meeting]

'''Tuesday September 7th 2010 12:00 UTC'''

* Tool maintainers and substitutes
* Release practices
* Status check of bugs and development

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-07-11.57.html Minutes of the meeting]

'''Tuesday August 31th 2010 12:00 UTC'''

* Short intro for project targets and tools we work with
* Status of open bugs / features at [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=eat&component=min&component=testdefinition&component=testrunner-lite&product=Development%20Tools bugs.meego.com]
* Review of released demo videos
* Review of contribution guidelines

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-31-11.57.html Minutes of the meeting]

Quality/QA tools development

2011-04-27T07:56:38Z

Asinnela: /* Meetings */

= QA tools development =

This page provides information on the development activities and practices of QA tools. The focus is on presenting things that are relevant for people interested in developing the tools. The main page for the end users is [[Quality/QA-tools|here]].

Anyone is welcome to contribute and non-member contributions will be treated with same process and review as member contributions. We follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://meego.gitorious.org/meego-quality-assurance/ git repositories] and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.

'''Targets:'''

* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance
* Improve MeeGo test automation (execution and software installation) - target from MeeGo release engineering

"As Core OS release release manager I want to verify trunk:testing packages frequently so that I know the quality of nightly/weekly releases."

== Tools and Maintainers ==

Tool maintainers are selected based on developer experience with particular tool/package or seniority. Tool maintainers have been agreed [[Quality/QA-tools/Meetings|in the QA-tools meeting]] Tuesday September 7th 2010. Changes, if needed, are discussed also there.

In practice only tool maintainers will have commit and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Others must follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines] to submit patches or personal clone + merge request approach.

The maintainer of the tree shall update the changelog.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Gitorious'''||'''Maintainer''' ||'''Substitute'''
|-
| [[Quality/QA-tools/Test-definition|test-definition]]||[http://meego.gitorious.org/meego-quality-assurance/test-definition Gitorious] || Sampo Saaristo || Timo Härkönen
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||[http://meego.gitorious.org/meego-quality-assurance/testrunner-lite Gitorious] || Sampo Saaristo || Kyösti Ranto
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || [http://meego.gitorious.org/meego-quality-assurance/testrunner Gitorious] || Kyösti Ranto || Timo Härkönen
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] ||[http://meego.gitorious.org/meego-quality-assurance/testplanner Gitorious] || Kyösti Ranto || N/A
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] ||[http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing Gitorious] || Timo Härkönen || Timo Mäkimattila
|-
| [[Quality/QA-tools/OTS|ots - open testing system]] ||[http://meego.gitorious.org/meego-quality-assurance/ots Gitorious] || Teemu Vainio || Tom Galvin
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||[http://gitorious.org/qa-tools/meego-ai Gitorious] || Timo Härkönen || N/A
|-
| [[Quality/TestSuite/MCTS|MeeGo Core Test Suite]] || [http://meego.gitorious.org/meego-quality-assurance/mcts/ Gitorious] ||Matti Salmi || Jeff Zheng
|-
| [[Quality/Netbook Test Suite and Utilities|MeeGo Netbook Test Suite]] || [http://gitorious.org/qa-tools/mnts/ Gitorious] ||Jeff Zheng || N/A
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || [http://gitorious.org/qa-tools/qtuitest-mbt-adapter Gitorious] || Riku Halonen || N/A
|-
| [http://min.sourceforge.net/ MIN test framework] || [http://meego.gitorious.org/meego-quality-assurance/min Gitorious] || Sampo Saaristo || Timo Mäkimattila
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || [http://gitorious.org/TDriver Gitorious] || Petri Kiiskinen || Tatu Lahtela
|-
| Rich Core dumper || [http://meego.gitorious.org/meego-quality-assurance/rich-core Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter settings || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter-settings-public Gitorious] || Carol Rus || Raimo Gratseff
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] || [http://meego.gitorious.org/meego-quality-assurance/hat-control Gitorious] || Marko Junttila || Riku Halonen
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || [http://meego.gitorious.org/meego-quality-assurance/qa-reports Gitorious] || Sami Hangaslammi || Jarno Keskikangas
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || [http://meego.gitorious.com/meego-quality-assurance/scripts-and-utils Gitorious] || N/A || N/A
|-
| [[Quality/TestSuite/handset-test-suite/handset-ux-test_Releases | handset_ux_tests]] || [http://meego.gitorious.com/meego-quality-assurance/handset-ux-tests Gitorious] || JessicaJi || N/A
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] || [http://meego.gitorious.org/meego-quality-assurance/meego-testing-hudson-plugin Gitorious] || Alexey Kuznetsov || Timo Härkönen
|-
| Service OS based Flasher || [http://meego.gitorious.org/meego-quality-assurance/meego-ai-serviceos Gitorious] || Jing Wang || N/A
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] || [http://meego.gitorious.org/meego-quality-assurance/libcqpid Gitorious] || Sami Lahtinen || N/A
|}

If you are interested in the user experience work regarding these tools, you can find more information [[Quality/QA-tools/User experience|here]].

=== Overview ===

The figure below tries to summarize the relations and tasks of the tools when used in test automation context.

[[File:testautomationtools.png]]

xfig file:[[File:qatools.fig]]

== Release Practices ==

Here is the workflow for QA tools release practices.

{| border="1" cellspacing="0"
|+
|'''Role'''
|'''Description'''
|-
| Developer || Anyone who wants to participate in qa-tools development
|-
| VCS Maintainer || Component owner who has commit rights in version control system (VCS)
|-
| Package Maintainer || Integrator whose responsibility is the OBS packaging
|-
| Release Management || Third party who is responsible of trunk:testing releases(?)
|}

[[File:Release.png]]

Kivio file: [[File:Release.flw]]

# Developer creates merge request(s) in gitorious.
# VCS Maintainer tests and accepts merge requests.
# VCS Maintainer checks/updates change logs.
# VCS Maintainer tags a version.
# VCS maintainer sends email to [http://lists.meego.com/pipermail/meego-qa/ meego-qa mailing list] based on the following template
Topic: Integration request: package-name version
PACKAGE: package-name
TAG: tag name
URL: link to sources
CHANGES: short description of changes containing bugs.meego.com bug numbers of fixed bugs
# Package maintainer updates the OBS package.
# Package maintainer tests the OBS package.
# If the package belongs to tools:testing and passes testing, Package Maintainer may accept it. If the package belongs to trunk:testing, Package Maintainer creates a promotional request to Release Management. (If the package belongs to both repositories, we let the Release Management set bugs fixed by the package to RELEASED state).
# Host side tools are updated to tools:testing after verifying functionality
# Package maintainer replies to meego-qa list about the actions done with the updated package. e.g. 'Updated in devel:quality and sent promotion request to testing'
# Release Management accepts the package. Or not. (Follow meego-packaging and meego-commits.)

''' YouTube videos '''

YouTube is a good way to communicate new features. You can find existing demo videos on [http://www.youtube.com/user/meegoqatools meegoqatools channel on Youtube].

If you shoot a video to YouTube, promote it on meego-qa mailing list!

You can find some hints how to shoot, edit, and upload a video here: [[YouTube_Hints]]

=== Release checklist ===
To make sure fixes are released without delay, check that the following conditions are met

# Change logs are updated and contain relevant references to MeeGo bugzilla
# Created obs request include fixes bug numbers from MeeGo bugzilla
# Bugzilla items listed in changes are set as resolved
# Spec file matches [[Packaging/Guidelines|MeeGo packaging guidelines]]
# Rpmlint warnings are either fixed or explained by comments in the spec file. e.g. eat packages install files into root's home and the reasoning for it needs to be explained
# Host side tool packages use the same source tar ball to produce debian and rpm packages

== Roadmap ==

The focus is currently on [[ARM/N900/QA|N900 Developer Edition QA]]. Hence the N900 related list below doesn't have a comprehensive information about target builds or priorities.

When you add a new bug, add correct dependencies to the corresponding roadmap meta bug.

The features in the roadmap are followed with META FEA bugs. The features are split to small tool specific FEA:s that block the feature META bug. The META bug is then the last bug to be closed when the feature is finished. You can also follow the tool bug progression from the dependency trees of the META bugs.

Adding a new feature to the roadmap:
# Add a feature bug describing the main purpose of the feature with META and FEA tags.
# Add separate bugs for each tool specific change
# Add correct dependencies between tool specific bugs (e.g. testrunner bug depends on testrunner-lite bug that depends on test-definition bug...)
# Make all of the bugs block the META bug

A list of defined features:

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12980&hide_resolved=0 Measurement support]
|-
| [https://bugs.meego.com/show_bug.cgi?id=12810 Easy install]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12454&hide_resolved=0 Parallel testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12981&hide_resolved=0 Events feature in automatic testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12937&hide_resolved=0 MCTS coverage support]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12833&hide_resolved=0 Test environment validation]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=13092&hide_resolved=0 Test equipment control]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12971&hide_resolved=0 Qt Creator integration]
|-
| [https://bugs.meego.com/show_bug.cgi?id=13190 A tool that combines Testrunner and Testplanner]
|-
| [[Quality/QA-tools/OTS/Roadmap|OTS releases]]
|}

== Design/ Planning ==

* [[Quality/QA-tools/MCTS test automation design|MCTS Test Automation]] (QA Tools support for MCTS)

== Documentation ==

Please make sure that all the relevant documentation regarding the tools is kept up-to-date whenever you update any of the tools. Please consider the end users of the tool as the primary readers of the documentation and make the documentation task-oriented for end user needs. Separate developer documentation can exist as well.

'''Wiki guidelines'''

Every tool should have a wiki page that contains at least 1) Overview of the tool and its benefits 2) Installation instructions 3) Basic use tutorial 4) Contact information.

Make sure that you are familiar with [[Wiki contribution guidelines|MeeGo wiki contribution guidelines]] before creating new content. Currently, there are quite a lot problems relating to e.g. page names, wiki links, deep hierarchies and obsolete pages in our wiki section.

'''Documentation checklist'''

The following table lists the tool-specific documentation that should exist (marked with 'x'). These should be checked frequently and more in depth in the future. Bugs will be filed for the missing or inaccurate documentation (marked as 'NOK' i.e. "Not OK").

{| border="1" cellspacing="0"
|+
|'''Tool''' ||'''Doxygen'''||'''Help''' ||'''Man pages''' || '''Wiki'''
|-
| test-definition || || || || x Checked: asinnela 2011-03-03
|-
| testrunner-lite || x || x Checked: asinnela 2011-03-07 || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14074 Bug 14074] || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14073 Bug 14073]
|-
| Testrunner || x || x Checked: asinnela 2011-03-07 || || x Checked: asinnela 2011-03-07
|-
| Testplanner || x || x Checked: asinnela 2011-03-10 || || x Checked: asinnela 2011-03-07
|-
| eat - enables automated testing || || || || x Checked: asinnela 2011-03-08
|-
| ots - open testing system || x || x || x || x Checked: asinnela 2011-03-25
|-
| MIN test framework || x || x || x ||
|-
| Scripts and utils || || || || x Checked: asinnela 2011-03-11
|-
| MeeGo Fast Feedback Testing || x || x || || x Checked: asinnela 2011-03-11
|-
| Qpid C wrapper library - libcqpid || x || || || x Page created, content to be added.
|}

'''Other documentation'''

* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]
* [[Quality/QA-tools/How_to_set_up_repositories|How to set up the repositories that are needed to install QA tools]]

== Meetings ==

All meetings will be held in <code>#meego-meeting</code> on <code>irc.freenode.net</code>.

* Team meetings
** QA-tools weekly meetings are held on every Tuesday 08:00 UTC in #meego-meeting2 on irc.freenode.net (please note the "2") from May 3rd 2011 onwards.
** [[Quality/QA-tools/Meetings|Meeting agendas and minutes]]

* Architecture meetings
** Architecture meetings will be held on-demand basis.
** [[Quality/QA-tools/Arch-Meetings|Meeting agendas and minutes]]

* Workshops
** Face-2-face meetings within the team.
** [[Quality/QA-tools/Workshops|Meeting agendas and minutes]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
** Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
** [http://timoph.fi/qa-tools-stats/ Old #meego-qa-tools statistics]
** [http://timoph.fi/qa-tools-logs-archive/ Archived #meego-qa-tools logs]
* Gitorious team, http://meego.gitorious.org/meego-quality-assurance/
* [http://www.youtube.com/user/meegoqatools Youtube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]
* MeeGo OBS - devel:quality
* This wiki area
* [[Quality/QA-tools/ServiceOS|ServiceOS]]
* [[Quality/QA-tools/PXEInstall|PXEInstallation]]

== Team members ==

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
| '''Name'''
| '''Role'''
| '''Affiliation'''
| '''IRC nickname'''
|-
| Ville Ilvonen || Team lead || Nokia || vilvo
|-
| Riku Halonen || Team member || Nokia || rikhalon
|-
| Kari Sievi || Team member || Digia || sievi
|-
| Timo Härkönen || Team member || Digia || timoph
|-
| Carol Rus || Team member || Digia || carrus
|-
| Sami Lahtinen || Team member || Digia || slahtinen
|-
| Raimo Gratseff || Team member || Digia || rrraimo
|-
| Kyösti Ranto || Team member || Digia || kyranto
|-
| Arto Sinnelä || Team member || Digia || asinnela
|-
| Joonas Kylänpää || Team member || Digia || Kaadlajk
|-
| Timo Mäkimattila || Team member || Digia || timakima
|-
| Elias Luttinen || Team member || Digia || eluttine
|-
| Ville Niutanen || Team member || Digia || Villen
|-
| Esa-Pekka Miettinen || Team member || Digia || E-P
|-
| Vesa Poikajärvi || Team member || Digia || vesse
|-
| Alexey Kuznetsov || Team member || Digia || alkuznet
|-
| Sergey Timofeev || Team member || Digia || setimofe
|-
| Daniil Chuiko || Team member || Digia || dachuiko
|-
| Jarmo Savinen || Team member || Digia || jasavi
|-
| Sampo Saaristo || Team member || Sofica || sampos
|-
| Ling Yu || Team member || Intel || -
|-
| Jing Wang || Team member || Intel || -
|-
| Teemu Vainio || Team member || Ixonos || tvainio
|-
| Tuomo Mäkinen || Team member || Ixonos || -
|-
| Jouni Leppäkases || Team member || Ixonos || jouni
|-
| Tom Galvin || Team member || Ixonos || -
|-
| Jarno Keskikangas || Team member || Leonidas || jakeskik
|-
| Janne Hietamäki || Team member || Leonidas || _janne
|-
| Sami Hangaslammi || Team member || Leonidas || sahangas
|-
|}

 
[[Category:QA]]

Quality/QA tools development

2011-04-27T07:56:20Z

Asinnela: /* Meetings */

= QA tools development =

This page provides information on the development activities and practices of QA tools. The focus is on presenting things that are relevant for people interested in developing the tools. The main page for the end users is [[Quality/QA-tools|here]].

Anyone is welcome to contribute and non-member contributions will be treated with same process and review as member contributions. We follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://meego.gitorious.org/meego-quality-assurance/ git repositories] and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.

'''Targets:'''

* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance
* Improve MeeGo test automation (execution and software installation) - target from MeeGo release engineering

"As Core OS release release manager I want to verify trunk:testing packages frequently so that I know the quality of nightly/weekly releases."

== Tools and Maintainers ==

Tool maintainers are selected based on developer experience with particular tool/package or seniority. Tool maintainers have been agreed [[Quality/QA-tools/Meetings|in the QA-tools meeting]] Tuesday September 7th 2010. Changes, if needed, are discussed also there.

In practice only tool maintainers will have commit and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Others must follow [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines] to submit patches or personal clone + merge request approach.

The maintainer of the tree shall update the changelog.

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Gitorious'''||'''Maintainer''' ||'''Substitute'''
|-
| [[Quality/QA-tools/Test-definition|test-definition]]||[http://meego.gitorious.org/meego-quality-assurance/test-definition Gitorious] || Sampo Saaristo || Timo Härkönen
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||[http://meego.gitorious.org/meego-quality-assurance/testrunner-lite Gitorious] || Sampo Saaristo || Kyösti Ranto
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || [http://meego.gitorious.org/meego-quality-assurance/testrunner Gitorious] || Kyösti Ranto || Timo Härkönen
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] ||[http://meego.gitorious.org/meego-quality-assurance/testplanner Gitorious] || Kyösti Ranto || N/A
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] ||[http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing Gitorious] || Timo Härkönen || Timo Mäkimattila
|-
| [[Quality/QA-tools/OTS|ots - open testing system]] ||[http://meego.gitorious.org/meego-quality-assurance/ots Gitorious] || Teemu Vainio || Tom Galvin
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||[http://gitorious.org/qa-tools/meego-ai Gitorious] || Timo Härkönen || N/A
|-
| [[Quality/TestSuite/MCTS|MeeGo Core Test Suite]] || [http://meego.gitorious.org/meego-quality-assurance/mcts/ Gitorious] ||Matti Salmi || Jeff Zheng
|-
| [[Quality/Netbook Test Suite and Utilities|MeeGo Netbook Test Suite]] || [http://gitorious.org/qa-tools/mnts/ Gitorious] ||Jeff Zheng || N/A
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || [http://gitorious.org/qa-tools/qtuitest-mbt-adapter Gitorious] || Riku Halonen || N/A
|-
| [http://min.sourceforge.net/ MIN test framework] || [http://meego.gitorious.org/meego-quality-assurance/min Gitorious] || Sampo Saaristo || Timo Mäkimattila
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || [http://gitorious.org/TDriver Gitorious] || Petri Kiiskinen || Tatu Lahtela
|-
| Rich Core dumper || [http://meego.gitorious.org/meego-quality-assurance/rich-core Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter Gitorious] || Carol Rus || Raimo Gratseff
|-
| Crash Reporter settings || [http://meego.gitorious.org/meego-quality-assurance/crash-reporter-settings-public Gitorious] || Carol Rus || Raimo Gratseff
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] || [http://meego.gitorious.org/meego-quality-assurance/hat-control Gitorious] || Marko Junttila || Riku Halonen
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || [http://meego.gitorious.org/meego-quality-assurance/qa-reports Gitorious] || Sami Hangaslammi || Jarno Keskikangas
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || [http://meego.gitorious.com/meego-quality-assurance/scripts-and-utils Gitorious] || N/A || N/A
|-
| [[Quality/TestSuite/handset-test-suite/handset-ux-test_Releases | handset_ux_tests]] || [http://meego.gitorious.com/meego-quality-assurance/handset-ux-tests Gitorious] || JessicaJi || N/A
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] || [http://meego.gitorious.org/meego-quality-assurance/meego-testing-hudson-plugin Gitorious] || Alexey Kuznetsov || Timo Härkönen
|-
| Service OS based Flasher || [http://meego.gitorious.org/meego-quality-assurance/meego-ai-serviceos Gitorious] || Jing Wang || N/A
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] || [http://meego.gitorious.org/meego-quality-assurance/libcqpid Gitorious] || Sami Lahtinen || N/A
|}

If you are interested in the user experience work regarding these tools, you can find more information [[Quality/QA-tools/User experience|here]].

=== Overview ===

The figure below tries to summarize the relations and tasks of the tools when used in test automation context.

[[File:testautomationtools.png]]

xfig file:[[File:qatools.fig]]

== Release Practices ==

Here is the workflow for QA tools release practices.

{| border="1" cellspacing="0"
|+
|'''Role'''
|'''Description'''
|-
| Developer || Anyone who wants to participate in qa-tools development
|-
| VCS Maintainer || Component owner who has commit rights in version control system (VCS)
|-
| Package Maintainer || Integrator whose responsibility is the OBS packaging
|-
| Release Management || Third party who is responsible of trunk:testing releases(?)
|}

[[File:Release.png]]

Kivio file: [[File:Release.flw]]

# Developer creates merge request(s) in gitorious.
# VCS Maintainer tests and accepts merge requests.
# VCS Maintainer checks/updates change logs.
# VCS Maintainer tags a version.
# VCS maintainer sends email to [http://lists.meego.com/pipermail/meego-qa/ meego-qa mailing list] based on the following template
Topic: Integration request: package-name version
PACKAGE: package-name
TAG: tag name
URL: link to sources
CHANGES: short description of changes containing bugs.meego.com bug numbers of fixed bugs
# Package maintainer updates the OBS package.
# Package maintainer tests the OBS package.
# If the package belongs to tools:testing and passes testing, Package Maintainer may accept it. If the package belongs to trunk:testing, Package Maintainer creates a promotional request to Release Management. (If the package belongs to both repositories, we let the Release Management set bugs fixed by the package to RELEASED state).
# Host side tools are updated to tools:testing after verifying functionality
# Package maintainer replies to meego-qa list about the actions done with the updated package. e.g. 'Updated in devel:quality and sent promotion request to testing'
# Release Management accepts the package. Or not. (Follow meego-packaging and meego-commits.)

''' YouTube videos '''

YouTube is a good way to communicate new features. You can find existing demo videos on [http://www.youtube.com/user/meegoqatools meegoqatools channel on Youtube].

If you shoot a video to YouTube, promote it on meego-qa mailing list!

You can find some hints how to shoot, edit, and upload a video here: [[YouTube_Hints]]

=== Release checklist ===
To make sure fixes are released without delay, check that the following conditions are met

# Change logs are updated and contain relevant references to MeeGo bugzilla
# Created obs request include fixes bug numbers from MeeGo bugzilla
# Bugzilla items listed in changes are set as resolved
# Spec file matches [[Packaging/Guidelines|MeeGo packaging guidelines]]
# Rpmlint warnings are either fixed or explained by comments in the spec file. e.g. eat packages install files into root's home and the reasoning for it needs to be explained
# Host side tool packages use the same source tar ball to produce debian and rpm packages

== Roadmap ==

The focus is currently on [[ARM/N900/QA|N900 Developer Edition QA]]. Hence the N900 related list below doesn't have a comprehensive information about target builds or priorities.

When you add a new bug, add correct dependencies to the corresponding roadmap meta bug.

The features in the roadmap are followed with META FEA bugs. The features are split to small tool specific FEA:s that block the feature META bug. The META bug is then the last bug to be closed when the feature is finished. You can also follow the tool bug progression from the dependency trees of the META bugs.

Adding a new feature to the roadmap:
# Add a feature bug describing the main purpose of the feature with META and FEA tags.
# Add separate bugs for each tool specific change
# Add correct dependencies between tool specific bugs (e.g. testrunner bug depends on testrunner-lite bug that depends on test-definition bug...)
# Make all of the bugs block the META bug

A list of defined features:

{| border="1" cellspacing="0"
|+
|'''Feature'''
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12980&hide_resolved=0 Measurement support]
|-
| [https://bugs.meego.com/show_bug.cgi?id=12810 Easy install]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12454&hide_resolved=0 Parallel testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12981&hide_resolved=0 Events feature in automatic testing]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12937&hide_resolved=0 MCTS coverage support]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=12833&hide_resolved=0 Test environment validation]
|-
| [http://bugs.meego.com/showdependencytree.cgi?id=13092&hide_resolved=0 Test equipment control]
|-
| [https://bugs.meego.com/showdependencytree.cgi?id=12971&hide_resolved=0 Qt Creator integration]
|-
| [https://bugs.meego.com/show_bug.cgi?id=13190 A tool that combines Testrunner and Testplanner]
|-
| [[Quality/QA-tools/OTS/Roadmap|OTS releases]]
|}

== Design/ Planning ==

* [[Quality/QA-tools/MCTS test automation design|MCTS Test Automation]] (QA Tools support for MCTS)

== Documentation ==

Please make sure that all the relevant documentation regarding the tools is kept up-to-date whenever you update any of the tools. Please consider the end users of the tool as the primary readers of the documentation and make the documentation task-oriented for end user needs. Separate developer documentation can exist as well.

'''Wiki guidelines'''

Every tool should have a wiki page that contains at least 1) Overview of the tool and its benefits 2) Installation instructions 3) Basic use tutorial 4) Contact information.

Make sure that you are familiar with [[Wiki contribution guidelines|MeeGo wiki contribution guidelines]] before creating new content. Currently, there are quite a lot problems relating to e.g. page names, wiki links, deep hierarchies and obsolete pages in our wiki section.

'''Documentation checklist'''

The following table lists the tool-specific documentation that should exist (marked with 'x'). These should be checked frequently and more in depth in the future. Bugs will be filed for the missing or inaccurate documentation (marked as 'NOK' i.e. "Not OK").

{| border="1" cellspacing="0"
|+
|'''Tool''' ||'''Doxygen'''||'''Help''' ||'''Man pages''' || '''Wiki'''
|-
| test-definition || || || || x Checked: asinnela 2011-03-03
|-
| testrunner-lite || x || x Checked: asinnela 2011-03-07 || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14074 Bug 14074] || x Checked: asinnela 2011-03-07, NOK [http://bugs.meego.com/show_bug.cgi?id=14073 Bug 14073]
|-
| Testrunner || x || x Checked: asinnela 2011-03-07 || || x Checked: asinnela 2011-03-07
|-
| Testplanner || x || x Checked: asinnela 2011-03-10 || || x Checked: asinnela 2011-03-07
|-
| eat - enables automated testing || || || || x Checked: asinnela 2011-03-08
|-
| ots - open testing system || x || x || x || x Checked: asinnela 2011-03-25
|-
| MIN test framework || x || x || x ||
|-
| Scripts and utils || || || || x Checked: asinnela 2011-03-11
|-
| MeeGo Fast Feedback Testing || x || x || || x Checked: asinnela 2011-03-11
|-
| Qpid C wrapper library - libcqpid || x || || || x Page created, content to be added.
|}

'''Other documentation'''

* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]
* [[Quality/QA-tools/How_to_set_up_repositories|How to set up the repositories that are needed to install QA tools]]

== Meetings ==

All meetings will be held in <code>#meego-meeting</code> on <code>irc.freenode.net</code>.

* Team meetings
** QA-tools weekly meetings are held every on Tuesday 08:00 UTC in #meego-meeting2 on irc.freenode.net (please note the "2") from May 3rd 2011 onwards.
** [[Quality/QA-tools/Meetings|Meeting agendas and minutes]]

* Architecture meetings
** Architecture meetings will be held on-demand basis.
** [[Quality/QA-tools/Arch-Meetings|Meeting agendas and minutes]]

* Workshops
** Face-2-face meetings within the team.
** [[Quality/QA-tools/Workshops|Meeting agendas and minutes]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
** Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
** [http://timoph.fi/qa-tools-stats/ Old #meego-qa-tools statistics]
** [http://timoph.fi/qa-tools-logs-archive/ Archived #meego-qa-tools logs]
* Gitorious team, http://meego.gitorious.org/meego-quality-assurance/
* [http://www.youtube.com/user/meegoqatools Youtube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]
* MeeGo OBS - devel:quality
* This wiki area
* [[Quality/QA-tools/ServiceOS|ServiceOS]]
* [[Quality/QA-tools/PXEInstall|PXEInstallation]]

== Team members ==

The current team members are (in no particular order):

{| border="1" cellspacing="0"
|+
| '''Name'''
| '''Role'''
| '''Affiliation'''
| '''IRC nickname'''
|-
| Ville Ilvonen || Team lead || Nokia || vilvo
|-
| Riku Halonen || Team member || Nokia || rikhalon
|-
| Kari Sievi || Team member || Digia || sievi
|-
| Timo Härkönen || Team member || Digia || timoph
|-
| Carol Rus || Team member || Digia || carrus
|-
| Sami Lahtinen || Team member || Digia || slahtinen
|-
| Raimo Gratseff || Team member || Digia || rrraimo
|-
| Kyösti Ranto || Team member || Digia || kyranto
|-
| Arto Sinnelä || Team member || Digia || asinnela
|-
| Joonas Kylänpää || Team member || Digia || Kaadlajk
|-
| Timo Mäkimattila || Team member || Digia || timakima
|-
| Elias Luttinen || Team member || Digia || eluttine
|-
| Ville Niutanen || Team member || Digia || Villen
|-
| Esa-Pekka Miettinen || Team member || Digia || E-P
|-
| Vesa Poikajärvi || Team member || Digia || vesse
|-
| Alexey Kuznetsov || Team member || Digia || alkuznet
|-
| Sergey Timofeev || Team member || Digia || setimofe
|-
| Daniil Chuiko || Team member || Digia || dachuiko
|-
| Jarmo Savinen || Team member || Digia || jasavi
|-
| Sampo Saaristo || Team member || Sofica || sampos
|-
| Ling Yu || Team member || Intel || -
|-
| Jing Wang || Team member || Intel || -
|-
| Teemu Vainio || Team member || Ixonos || tvainio
|-
| Tuomo Mäkinen || Team member || Ixonos || -
|-
| Jouni Leppäkases || Team member || Ixonos || jouni
|-
| Tom Galvin || Team member || Ixonos || -
|-
| Jarno Keskikangas || Team member || Leonidas || jakeskik
|-
| Janne Hietamäki || Team member || Leonidas || _janne
|-
| Sami Hangaslammi || Team member || Leonidas || sahangas
|-
|}

 
[[Category:QA]]

Quality/QA-tools/meetings

2011-04-26T10:59:25Z

Asinnela: Redirected page to Quality/QA-tools/Meetings

#REDIRECT [[Quality/QA-tools/Meetings]]

Quality/QA-tools/Meetings

2011-04-26T10:57:58Z

Asinnela:

= QA Tools - Weekly Meetings =

QA-tools weekly meetings are held every on Tuesday 08:00 UTC in <code>#meego-meeting2 on irc.freenode.net</code> (please note the "2") from May 3rd 2011 onwards.

== Next meeting ==

'''Tuesday May 3rd 2011 08:00 UTC''' - Agenda Proposal

* QA tools status update
* Any Other Business

== Previous Meeting Minutes ==

'''Tuesday December 7th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-11.59.html Minutes of the meeting]

'''Tuesday November 30rd 2010 12:00 UTC'''

* Regular Meeting Agenda
* Discussion on test report templates support at qa-reports.meego.com (#9922)

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-11.59.html Minutes of the meeting]

'''Tuesday November 23rd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-11.59.html Minutes of the meeting]

'''Tuesday November 16th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-16-11.59.html Minutes of the meeting]

'''Tuesday November 9th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-11.59.html Minutes of the meeting]

'''Tuesday November 2nd 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-02-12.06.html Minutes of the meeting]

'''Tuesday October 26th 2010 12:00 UTC'''

* Regular Meeting Agenda
* Co-maintainer for Tools:Testing

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-26-12.00.html Minutes of the meeting]

'''Tuesday October 19th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-19-12.00.html Minutes of the meeting]

'''Tuesday October 12th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-12-11.57.html Minutes of the meeting]

'''Tuesday October 5th 2010 12:00 UTC'''

* Regular Meeting Agenda

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-05-11.57.html Minutes of the meeting]

'''Tuesday September 28th 2010 12:00 UTC'''

* Action points from last meeting
* Released packages and videos
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-28-11.57.html Minutes of the meeting]

'''Tuesday September 21th 2010 12:00 UTC'''

* Action points from last meeting
* OTS client toolchain status
* Priorities of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-21-11.57.html Minutes of the meeting]

'''Tuesday September 14th 2010 12:00 UTC'''

* Action points from last meeting
* Review of Release Practices proposal (Timo Härkönen & Timo Mäkimattila)
* Status check of new development
* Status check of bugs

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-14-11.57.html Minutes of the meeting]

'''Tuesday September 7th 2010 12:00 UTC'''

* Tool maintainers and substitutes
* Release practices
* Status check of bugs and development

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-07-11.57.html Minutes of the meeting]

'''Tuesday August 31th 2010 12:00 UTC'''

* Short intro for project targets and tools we work with
* Status of open bugs / features at [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=eat&component=min&component=testdefinition&component=testrunner-lite&product=Development%20Tools bugs.meego.com]
* Review of released demo videos
* Review of contribution guidelines

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-31-11.57.html Minutes of the meeting]

Quality/TestSuite/MWTS Asset Buteo Description

2011-04-23T10:24:09Z

Asinnela: /* References */ Wiki link fix

= Introduction =

== Overview ==

{| border="1" cellspacing="0" cellpadding="5"
|'''Status'''
| In progress <del>>Released </del><del>Deprecated</del>
|-
|'''Maintainer'''
|Pauli-Pekka Toivanen
|-
|}

MWTS-Buteo asset tests buteo sync-framework apis.

The Buteo Sync solution is a complete solution that broadly provides the following synchronization services:

* Device to device synchronization of PIM data (Contacts and Calendar for now) based on SyncML
* Device to cloud synchronization of PIM data (ovi.com, Scheduleworld.com etc.) based on SyncML
* Synchronization of media content to PC based on MTP
* Device to PC synchronization (currently only OviSuite, but this requires contract with OviSuite to support a particular device)

Libs used are:

* sync-fw
* for building sync-fw-dev

== Getting the Latest Version ==

* http://gitorious.org/qa-tools/mcts/trees/master/mcts-mwts/generic/mwts-buteo

See chapter "running the test" for further instructions.

== Support & Contacts ==

* In case of a problem read carefully through this document. Then search bugzilla to see if someone else has had similar problems.
* If your questions is still valid, please prefer the public #meego-qa-mcts @ irc.freenode.net IRC-channel or meego-qa-tools mailing list. This way you get the best possible attention to your questions.
* If you think that you need to directly contact package maintainer then contact
** Pauli-Pekka Toivanen, pauli-pekka.toivanen@digia.com (you can also take a look at the authors file to find the people who to cc)

== Licensing ==
* Please see the file called COPYING

== Supported Devices and SW ==

mwts-buteo officially supports the following devices

* nCDK
* N900

Netbooks are not officially supported at the moment but it should work just fine on netbooks as well.

== Test Cases ==

Test cases located in files mwts-buteo.cfg & mwts-buteo-nft.cfg

{| border="1" cellspacing="0"
!Test case name
!Description
|-
|FUTE-Buteo_list_profiles
|Lists available sync profiles
|-
|FUTE-Buteo_create_btprofile
|Creates bluetooth sync profile
|-
|FUTE-Buteo_create_google_profile
|Creates google contacts sync profile
|-
|FUTE-Buteo_remove_bt_profile
|Removes bluetooth profile
|-
|FUTE-Buteo_remove_google_profile
|Removes google profile
|-
|FUTE-Buteo_remove_profiles
|Removes all profiles
|-
|FUTE-Buteo_sync_bt
|Syncs with bluetooth profile
|-
|FUTE-Buteo_sync_google
|Cloud syncs google contacts
|-
|FUTE-Buteo_sync_memotoo
|cloud Syncs with memotoo.com profile
|-
|FUTE-Buteo_sync_mobical
|Cloud syncs with mobical.com profile
|-
|FUTE-Buteo_sync_ovi
|Cloud syncs with ovi.com profile
|-
|NFT-Buteo_sync_bt-ITER
|Syncs with bluetooth profile
|-
|NFT-Buteo_sync_google-ITER
|Cloud syncs google contacts
|-
|NFT-Buteo_sync_memotoo-ITER
|cloud Syncs with memotoo.com profile
|-
|NFT-Buteo_sync_mobical-ITER
|Cloud syncs with mobical.com profile
|-
|NFT-Buteo_sync_ovi-ITER
|Cloud syncs with ovi.com profile
|-
|NFT-Buteo_sync_bt-LATE
|Syncs with bluetooth profile
|-
|NFT-Buteo_sync_google-LATE
|Cloud syncs google contacts
|-
|NFT-Buteo_sync_memotoo-LATE
|cloud Syncs with memotoo.com profile
|-
|NFT-Buteo_sync_mobical-LATE
|Cloud syncs with mobical.com profile
|-
|NFT-Buteo_sync_ovi-LATE
|Cloud syncs with ovi.com profile

|}

= Running the Tests =

== Hardware setup and test environment ==

'''Required HW & SW'''
* One test device with MeeGo
* Bluetooth hardware for bt syncing
* Internet connection for cloud syncing

'''Required SW'''
* Qt >= 4.7.0 version
* mwts-buteo
* mwts-common (use the latest version)
* synf-fw, sync-fw-dev package

If for some reason sync service plugins are missing, you can manually install them from the repositories. Different plugin are needed for different services (bluetooth, google, memotoo etc)
<pre>
zypper pa | grep buteo-service
zypper install buteo-service-google buteo-service-memotoo etc ...
</pre>
* sync service plugins packages for different cloud services (buteo-service-google, buteo-service-memotoo etc )

== Building packages ==
* Check that depended packages are installed (mwts-common-devel, sync-fw-dev)
* Execute buildrpm.sh script from the asset source root

* built rmps located in source root/rpm/RPMS/...
* Installation 'rpm -i <package_name>'

== Running test cases ==

Before running cases you need to set LD_LIBRARY_PATH enviroment variable to '/lib'. Use 'export LD_LIBRARY_PATH=/lib' and kill and restart msync-daemon. This is a current workaround and will change in future.

For cloud syncing you need to se up internet connection first. Account credentials need to be set in the config file first (/usr/lib/tests/ButeoTest.conf).

For bluetooth syncing you should pair your devices beforehand. Bluetooth adresses etc need to be set in the config file first (/usr/lib/tests/ButeoTest.conf).

Otherwise MWTS-Buteo test execution is performed normally. Check the "General MWTS testing guide".

== Test result analysis ==

Test result are available in the MIN UI. In addition, test result log files can be found from device in directory

/var/log/tests/

Result files are named according to test cases, <test_case_name>.result file contains overall information about test run and measured values.

== Troubleshooting ==
* Test logs show you if the the dbus-service from msyncd is working.

You can set sync-framework loggin on modifyind /etc/sync/set_sync_log_level files value to 4.
Also set enviromental variable LD_LIBRARY_PATH 'export LD_LIBRARY_PATH=/lib:$LD_LIBRARY_PATH' . Now you should be able to see debug in /home/meego/.sync/synchronizer.log.

== Configuration file examples ==
<pre>
[General]
sync_home=/home/meego/.sync/profiles/ # point to your users home directory

[bt_profile]
bt_address=00:00:00:00:00:00
bt_name=some_bt_dev
profile_name=bt_profile

[google_profile] # google.com
username=testipersoona
password=test
profile_name=google_profile

[memotoo_profile] # memotoo.com
username=testipersoona
password=test
profile_name=memotoo_profile

</pre>

= Module Design and Architecture =

== Architecture ==

* Synchronization Framework - a generic framework providing a pluggable architecture.
* SyncML stack - a OMA DS 1.1 and 1.2 compliant SyncML stack.
* MTP stack - A Media Transfer Protocol 1.0 compliant MTP implemenation.
* Sync plugins - a syncml sync plugin and a MTP sync plugin that hook into the synchronization framework

== MIN Scripter Interface ==

{| class="wikitable" cellspacing="0" border="1"
|-
! MIN
! Description
|-

| Sync <profile_name>
| Starts syncing according to given profile
|-

| RemoveProfile <profile_name>
| Removes created profile
|-

| RemoveProfiles
| Removes all profiles
|-

| ListProfiles
| Lists available profiles
|-

| CreateBtProfile <profile_name>
| Creates a bluetooth sync profile
|-

| CreateOviProfile
| Creates a ovi sync service profile
|-

| CreateGoogleProfile
| Creates a google sync service profile
|-

| CreateMobicalProfile
| Creates a mobical sync service profile
|-

| CreateMemotooProfile
| Creates a memotoo sync service profile
|-

|}

= Known issues =
* Currently missing some capabilities for services
* Before running cases you need to set LD_LIBRARY_PATH enviroment variable to '/lib'. Use 'export LD_LIBRARY_PATH=/lib' and kill and restart msync-daemon. This is a current workaround and will change in future.

= Future improvements =
* Cover more service and sync scenarios

= References =
* [[Buteo]]

MeeGo SDK Enabling QEMU

2011-04-23T10:14:39Z

Asinnela: Fixed double redirect

#REDIRECT [[SDK/Docs/1.1/MeeGo SDK Graphics Acceleration]]

MeeGo-Lem

2011-04-11T05:41:24Z

Asinnela: /* Google Chrome, Flash Plugins, Java, Skype, LibreOffice, etc. */ fixed wiki links

=MeeGo-Lem: Linux Everywhere for MeeGolem=

WARNING: THIS IS A WORK IN PROGRESS
STATUS: Not even close yet.

This is a guide on how to run and install Fedora's "noncompliant apps", along with the rest of Fedora14 libs and apps, on MeeGo 1.2 Netbook.
The intent here is not MeeGo non-compliance, but rather end-user usefulness, on-par with what other user's get from installing Fedora, and then following instructions like http://www.mjmwired.net/resources/mjm-fedora-f14.html to actually get a system that's worth using.

This hack provides the following repositories that work alongside MeeGo's if you're careful with your use of 'zypper'
* Fedora 14 from http://fedoraproject.org/
* Noncompliant and additional packages from http://rpmfusion.org/
* Audio/Video from http://ccrma.stanford.edu/planetccrma/software/
* Adobe's Flash Plugin RPM repository from http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3
* Google Chrome Browser RPM repository from http://www.google.com/chrome/eula.html?platform=linux

The end result is over [http://nielsmayer.com/meego/lem/meegolem-packagelist.txt 20000 packages] many of which work beautifully.

See http://lists.meego.com/pipermail/meego-community/2011-March/003675.html

https://bugs.meego.com/show_bug.cgi?id=14129

==Installation==

===Prerequisites===

* Setup sudo
...
* Install tar and wget
sudo zypper install tar wget
...

===Install repositories===

* /etc/zypp/repos.d/*.repo
cd /tmp ; wget 'https://bugs.meego.com/attachment.cgi?id=4761'
cd / ; tar xvzf '/tmp/attachment.cgi?id=4761'

* /etc/pki/rpm-gpg/*
cd /tmp ; wget 'https://bugs.meego.com/attachment.cgi?id=4762'
cd / ; tar xvzf '/tmp/attachment.cgi?id=4762'

===Refresh zypper===

$ sudo zypper clean --all
$ sudo zypper --gpg-auto-import-keys refresh

===The Hacks that Make it All Possible===

* Fedora uses readline6, MeeGo uses readline5.

* Fedora uses Python 2.7, MeeGo uses Python 2.6.

=Some Example Installations=

==Google Chrome, Flash Plugins, Java, Skype, LibreOffice, etc.==

* Simple install of google-chrome beta (and flash/java/talk) on MeeGo 1.2 Netbook
** see http://lists.meego.com/pipermail/meego-community/2011-February/003570.html

* Chrome: simple setup with LEM installed:

sudo zypper install google-chrome-beta
...
## note three different versions available:
$ zypper search chrome
...
i | google-chrome-beta | Google Chrome | package
| google-chrome-stable | Google Chrome | package
| google-chrome-unstable | Google Chrome | package
...

* Firefox4:
** Just-released [http://www.mozilla.com/en-US/firefox/4.0/releasenotes/ Firefox4] is packaged with Fedora 15.
** MeeGo, closer to Fedora 14, is supported by Fedora 'remi' ([http://forums.famillecollet.com/viewforum.php?id=5 Remi Collet] repositories).
** With LEM, http://www.if-not-true-then-false.com/2010/install-firefox-4-on-fedora/ is relatively straightforward.
** See: [[MeeGo-Lem-Firefox4]]

* Adobe Flash: simple setup with LEM installed:
** See: https://bugs.meego.com/show_bug.cgi?id=10894#c4

## install from Adobe RPM reposotory from LEM
$ sudo zypper install flash-plugin
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
flash-plugin
1 new package to install.
Overall download size: 4.7 MiB. After the operation, additional 11.6 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package flash-plugin-10.2.152.27-release.i386 (1/1), 4.7 MiB (11.6 MiB unpacked)
Retrieving: flash-plugin-10.2.152.27-release.i386.rpm [done (790.4 KiB/s)]
Installing: flash-plugin-10.2.152.27-release [done]

## Setup Link to enable web browser plugin:
$ sudo rm -f /usr/lib/mozilla/plugins/libflashplayer.so
$ sudo ln -s /usr/lib/flash-plugin/libflashplayer.so /usr/lib/mozilla/plugins/libflashplayer.so
## Now restart browser or qtwebkit-based apps requiring flash.

* Installing Skype on MeeGo 1.2 Netbook (doesn't use LEM since skype doesn't provide repository):
** Use browser to download Fedora RPM from http://www.skype.com/intl/en/get-skype/on-your-computer/linux/downloading.fedora
** Latest Skype intended for Fedora 13+ resolves issues from earlier versions: https://bugs.meego.com/show_bug.cgi?id=14117#c4
$ sudo rpm -ivh skype-2.2.0.25-fedora.i586.rpm
Failed to expand %__security_plugin macro
Preparing... ########################################### [100%]
1:skype ########################################### [100%]

* Install latest LibreOffice on MeeGo 1.2 Netbook:
** See: [[LibreOffice]]
** LibreOffice is recommended over Fedora's OpenOffice: http://forum.meego.com/showpost.php?p=18796&postcount=24 ; also Fedora provides a much older version than LibreOffice, and has special weird Fedora dependencies to the OpenJDK java included with Fedora.

==Be able to watch/hear common internet media formats==

Using LEM, follow instructions in http://www.mjmwired.net/resources/mjm-fedora-f14.html#mp3 and
http://www.mjmwired.net/resources/mjm-fedora-f14.html#mediaplayers to be able to hear MP3's or watch FLV, AVI or other "nonfree" codec-requiring formats.

$ sudo zypper in gstreamer-ffmpeg gstreamer-plugins-ugly gstreamer-plugins-bad
Loading repository data...
Reading installed packages...
'gstreamer-plugins-ugly' is already installed.
No update candidate for 'gstreamer-plugins-ugly-0.10.16-2.fc14.i686'. The highest available version is already installed.
Resolving package dependencies...

The following NEW packages are going to be installed:
gstreamer-ffmpeg gstreamer-plugins-bad gstreamer-plugins-bad-free libass
libcdaudio libkate libmimic libmms libofa libquicktime mjpegtools-libs

11 new packages to install.
Overall download size: 2.2 MiB. After the operation, additional 6.4 MiB will be
used.
Continue? [y/n/?] (y): y
Retrieving package libmms-0.6.2-1.fc14.i686 (1/11), 48.0 KiB (108.0 KiB unpacked)
Retrieving: libmms-0.6.2-1.fc14.i686.rpm [done (7.6 KiB/s)]
Retrieving package libquicktime-1.1.5-2.fc14.i686 (2/11), 283.0 KiB (857.0 KiB unpacked)
Retrieving: libquicktime-1.1.5-2.fc14.i686.rpm [done (20.5 KiB/s)]
Retrieving package libmimic-1.0.4-4.fc12.i686 (3/11), 28.0 KiB (78.0 KiB unpacked)
Retrieving: libmimic-1.0.4-4.fc12.i686.rpm [done]
Retrieving package gstreamer-ffmpeg-0.10.11-1.fc14.i686 (4/11), 169.0 KiB (494.0 KiB unpacked)
Retrieving: gstreamer-ffmpeg-0.10.11-1.fc14.i686.rpm [done (83.3 KiB/s)]
Retrieving package libofa-0.9.3-16.fc12.i686 (5/11), 56.0 KiB (154.0 KiB unpacked)
Retrieving: libofa-0.9.3-16.fc12.i686.rpm [done (1.3 KiB/s)]
Retrieving package libass-0.9.11-1.fc14.i686 (6/11), 62.0 KiB (125.0 KiB unpacked)
Retrieving: libass-0.9.11-1.fc14.i686.rpm [done (16.1 KiB/s)]
Retrieving package libcdaudio-0.99.12p2-13.fc12.i686 (7/11), 38.0 KiB (81.0 KiB unpacked)
Retrieving: libcdaudio-0.99.12p2-13.fc12.i686.rpm [done (6.6 KiB/s)]
Retrieving package libkate-0.3.7-2.fc14.i686 (8/11), 46.0 KiB (92.0 KiB unpacked)
Retrieving: libkate-0.3.7-2.fc14.i686.rpm [done (13.6 KiB/s)]
Retrieving package mjpegtools-libs-1.9.0-2.fc14.i686 (9/11), 233.0 KiB (581.0 KiB unpacked)
Retrieving: mjpegtools-libs-1.9.0-2.fc14.i686.rpm [done (58.4 KiB/s)]
Retrieving package gstreamer-plugins-bad-free-0.10.20-3.fc14.i686 (10/11), 1.0 MiB (3.3 MiB unpacked)
Retrieving: gstreamer-plugins-bad-free-0.10.20-3.fc14.i686.rpm [done (356.9 KiB/s)]
Retrieving package gstreamer-plugins-bad-0.10.20-2.fc14.i686 (11/11), 241.0 KiB (679.0 KiB unpacked)
Retrieving: gstreamer-plugins-bad-0.10.20-2.fc14.i686.rpm [done (40.1 KiB/s)]
Installing: libmms-0.6.2-1.fc14 [done]
Installing: libquicktime-1.1.5-2.fc14 [done]
Installing: libmimic-1.0.4-4.fc12 [done]
Installing: gstreamer-ffmpeg-0.10.11-1.fc14 [done]
Installing: libofa-0.9.3-16.fc12 [done]
Installing: libass-0.9.11-1.fc14 [done]
Installing: libcdaudio-0.99.12p2-13.fc12 [done]
Installing: libkate-0.3.7-2.fc14 [done]
Installing: mjpegtools-libs-1.9.0-2.fc14 [done]
Installing: gstreamer-plugins-bad-free-0.10.20-3.fc14 [done]
Installing: gstreamer-plugins-bad-0.10.20-2.fc14 [done]
$ sudo zypper in xine-lib-extras-freeworld ffmpeg2dirac ffmpeg2theora ffmpegthumbnailer
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
ffmpeg2dirac ffmpeg2theora ffmpegthumbnailer liboil vcdimager vcdimager-libs
xine-lib-extras-freeworld

7 new packages to install.
Overall download size: 999.0 KiB. After the operation, additional 3.1 MiB will
be used.
Continue? [y/n/?] (y): y
Retrieving package ffmpegthumbnailer-2.0.6-1.fc14.i686 (1/7), 55.0 KiB (171.0 KiB unpacked)
Retrieving: ffmpegthumbnailer-2.0.6-1.fc14.i686.rpm [done]
Retrieving package vcdimager-0.7.23-13.fc13.1.i686 (2/7), 300.0 KiB (1.1 MiB unpacked)
Retrieving: vcdimager-0.7.23-13.fc13.1.i686.rpm [done (14.5 KiB/s)]
Retrieving package ffmpeg2theora-0.27-1.fc14.i686 (3/7), 61.0 KiB (149.0 KiB unpacked)
Retrieving: ffmpeg2theora-0.27-1.fc14.i686.rpm [done]
Retrieving package liboil-0.3.16-4.fc12.i686 (4/7), 113.0 KiB (497.0 KiB unpacked)
Retrieving: liboil-0.3.16-4.fc12.i686.rpm [done (35.7 KiB/s)]
Retrieving package vcdimager-libs-0.7.23-13.fc13.1.i686 (5/7), 96.0 KiB (187.0 KiB unpacked)
Retrieving: vcdimager-libs-0.7.23-13.fc13.1.i686.rpm [done (39.7 KiB/s)]
Retrieving package ffmpeg2dirac-0.1.0-4.fc12.i686 (6/7), 49.0 KiB (102.0 KiB unpacked)
Retrieving: ffmpeg2dirac-0.1.0-4.fc12.i686.rpm [done (20.4 KiB/s)]
Retrieving package xine-lib-extras-freeworld-1.1.19-1.fc14.i686 (7/7), 325.0 KiB (889.0 KiB unpacked)
Retrieving: xine-lib-extras-freeworld-1.1.19-1.fc14.i686.rpm [done (20.2 KiB/s)]
Installing: ffmpegthumbnailer-2.0.6-1.fc14 [done]
Installing: vcdimager-0.7.23-13.fc13.1 [done]
Installing: ffmpeg2theora-0.27-1.fc14 [done]
Installing: liboil-0.3.16-4.fc12 [done]
Installing: vcdimager-libs-0.7.23-13.fc13.1 [done]
Installing: ffmpeg2dirac-0.1.0-4.fc12 [done]
Installing: xine-lib-extras-freeworld-1.1.19-1.fc14 [done]
$ sudo zypper in mplayer-gui gecko-mediaplayer mencoder ## see http://www.mjmwired.net/resources/mjm-fedora-f14.html#mediaplayers
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
gecko-mediaplayer gnome-mplayer-common gnome-mplayer-minimal mencoder
mplayer-gui

5 new packages to install.
Overall download size: 7.1 MiB. After the operation, additional 18.6 MiB will
be used.
Continue? [y/n/?] (y): y
Retrieving package gnome-mplayer-common-1.0.0-1.fc14.i686 (1/5), 210.0 KiB (858.0 KiB unpacked)
Retrieving: gnome-mplayer-common-1.0.0-1.fc14.i686.rpm [done (37.2 KiB/s)]
Retrieving package mplayer-gui-1.0-0.119.20100703svn.fc14.i686 (2/5), 3.5 MiB (9.0 MiB unpacked)
Retrieving: mplayer-gui-1.0-0.119.20100703svn.fc14.i686.rpm [done (113.1 KiB/s)]
Retrieving package mencoder-1.0-0.119.20100703svn.fc14.i686 (3/5), 3.1 MiB (8.0 MiB unpacked)
Retrieving: mencoder-1.0-0.119.20100703svn.fc14.i686.rpm [done (105.1 KiB/s)]
Retrieving package gnome-mplayer-minimal-1.0.0-1.fc14.i686 (4/5), 114.0 KiB (319.0 KiB unpacked)
Retrieving: gnome-mplayer-minimal-1.0.0-1.fc14.i686.rpm [done (23.3 KiB/s)]
Retrieving package gecko-mediaplayer-1.0.0-1.fc14.i686 (5/5), 78.0 KiB (493.0 KiB unpacked)
Retrieving: gecko-mediaplayer-1.0.0-1.fc14.i686.rpm [done]
Installing: gnome-mplayer-common-1.0.0-1.fc14 [done]
Installing: mplayer-gui-1.0-0.119.20100703svn.fc14 [done]
Installing: mencoder-1.0-0.119.20100703svn.fc14 [done]
Installing: gnome-mplayer-minimal-1.0.0-1.fc14 [done]
Installing: gecko-mediaplayer-1.0.0-1.fc14 [done]

$ killall -HUP banshee-1 ##must kill and restart banshee
$ banshee-1 ##start from commandline to see entertaining error messages https://bugs.meego.com/show_bug.cgi?id=14658

The end result -- you can watch FLV video downloaded from youtube:

[[file:Banshee-on-meegolem-playing-flv-via-nonfree-gsteamer-ffmpeg-plugins.png]]

The [http://code.google.com/p/gecko-mediaplayer/ gecko-mediaplayer plugin] installed above, allows media to be viewed directly in the web browser:

[[File:Chrome-with-gecko-mediaplayer-on-meegolem.png]]

==smplayer for streaming audio/video playback==

[[File:Smplayer-on-meegolem.png]]

==gpodder and needed python plugins -- to watch/manage podcasts==

[[File:Gpodder-on-meegolem.png]]

==The OpenShot Video Editor==

[[file:Openshot-on-meegolem.png]]

==The Jack Audio Connection Kit, QJackCtl, and Various Cool Audio Tools==

[[file:Qjackctl-on-meegolem.png]]
[[file:qjackctl-connections-on-meegolem.png]]
[[file:Jack-alsa-audio-analyser-on-meegolem.png]]
[[file:Jack-audio-applications-on-meegolem.png]]
[[file:Jack-alsa-perceptual-analyser.png]]

==Qtractor Audio/MIDI Editor and Sound processing plugins==

[[File:Qtractor-plastique-style-on-meegolem.png]]
[[File:Qtractor-dialogs-plastique-style-meego.png]]

==Games Games Games!==

(Author doesn't have time for games, but notes a fully populated installer, and son happy with MeeGo on his netbook).

[[File:meego-installer-on-meegolem.png]]

ARM/Hummingbird

2011-04-09T13:31:04Z

Asinnela: /* Build */ Wiki link fix

= Nexus S =

[[File:DSC00579.jpg|400px]]
[[File:nexuss.jpg|400px]]

So, I have a barebones version of MeeGo (barely) running on the Nexus S. I can't really do much with it on my own, but I'm posting the info here so you can build it and try it for yourself.

== What works ==

* ADB root shell
* X11 & UI apps
* Screen brightness

== What doesn't work ==

* Touchscreen
* WiFi
* Anything else :-P

== Build ==
*Use the procedure here to generate an ext2 image, and copy it to linux/rootfs.ext2 on the internal memory of the Nexus S. [[ARM/Meego_on_Beagleboard_from_scratch#Build_the_rootfs]]

I have my boot.img (kernel + ramdisk) and a MeeGo kickstart file at http://blog.steventroughtonsmith.com/2011/01/nexus-s-meego.html; you can use fastboot to boot the image, or flash it to the recovery partition to dual boot. The actual MeeGo rootfs is run from a rootfs.ext2 file you can drop onto the Nexus S using Mass Storage mode - no need for messy flashing or the like, you can thank me later).

There's not much else I can do on my own right now, so if you want to see anything become of this do get involved!

== Kernel ==

My kernel is Samsung stock; you will need to modify it to get X11 to run:

* git://android.git.kernel.org/kernel/samsung.git
* make herring_defconfig

The only change was modifying the .config file to turn on CONFIG_VT (needed for X11, unless we [http://code.google.com/p/savory/source/browse/trunk/x11-on-kindle/xorg-1.6.patch?r=14 recompile X11 without VT support]).

== Screen brightness ==
Will add this to a newer kickstart, but for the time being, you can bring the brightness to full by doing:

* echo 255 > /sys/devices/platform/s3cfb/spi_gpio.3/spi3.0/backlight/s5p_bl/brightness

== Notes ==
dmesg output is available on [[Talk:ARM/Hummingbird]].

= Samsung Galaxy Tab =

WORK IN PROGRESS, I'M STILL ADDING INFO! - 16/2/2011
If you're in a desperate hurry then feel free to catch me (lardman) on #meego-arm and pick my brain/add info/make changes here/etc. :)

== Meego ==

=== Current Status ===

Working:
* Boots Meego (external SD btrfs partition or ext2 loop file)
* Wifi working (so you can login)
* Tab kb dock working (so you can login)
* Basic unaccelerated X on the framebuffer. (Requires small kernel patch) - kernel patch not necessary now, just "echo 1 > /sys/class/lcd/s5p_lcd/lcd_power" after you start Xorg to switch display on.
* Basic audio playback (The soundcard acts funny unless you feed it 32kHz audio, and on playback you need to run (amixer sset "Playback Path" "SPK") to actually enable sound)
* Touch screen - Basic single touch working, using the mtev driver.

In progress:
* PowerVR accelerated UI - We have the source for the Android kernel driver (look on the Samsung opensource site for the Galaxy S (I9000) source). It appears to still have the XOrg code in place, but the build infrastructure is gone. I've been playing around with merging it in from the PandaBoard SGX drivers, and have gotten something to compile and load on the Tab - but that's about it. (From my understanding, there are two parts to the SGX drivers, the closed source userland - which we can steal from the PandaBoard - and the open source kernel driver. The open source kernel driver has two modes, Android and XOrg / DRI. It also requires a specific driver for the LCD and BC (bufferclass?), which we have as s3c_lcd and s3c_bc.)

Not tried yet:
* Bluetooth
* Modem
* GPS
* Camera
* DSP acceleration
* Sensors (compass, accelerometers)

If you would like to help, have questions, ideas, etc., please catch me (lardman) in #meego-arm

=== Introduction ===

The idea here is to boot Meego from the external SD card (similar to the N900 Meego boot process.)

Currently this requires that you flash a new, slightly modified, kernel to your Tab.

The Tab kernel contains an initramfs which contains an Android version of init which brings the system up.

With Android devices, there is normally a hardware key you can press at boot time to specify whether you want to enter flashing mode or recovery mode (and no keypress indicates a normal startup.) On the Tab the flashing key is the volume down button and the recovery button is the volume up button.

With most Android devices the normal and recovery boots load different kernels (located on different partitions.) This is nice as it means one does not need to modify the normal Android kernel at all, but can still mess about with other kernels in the recovery kernel partition (e.g. to try booting Meego, at the expense of no recovery mode, which is not a big problem.) But, in their infinite wisdom, Samsung decided that both normal and recovery modes would use the same kernel on the Tab. Rather than booting a completely separate kernel, the Tab boots the same kernel and the Android-specific init somehow recognises which mode was selected at boot time. It then proceeds to process either init.rc or recovery.rc.

Now this would give us an option of modifying the boot process, but the major problem is that while the Android init should support an exec command, this is not implemented in the version we have, and therefore even if we modify the recovery.rc file to try to start our own script to switch_root, etc., it won't work. The Android init used in the Tab is not stock Google code and there is no source available for the modifications.

Therefore I've renamed the Android init and replaced with it an init script which searches for Meego installations (btrfs partitions on the external SD card, or loop images) and if these are not found exec's the renamed Android init, which goes on its merry way and starts Android just like normal.

=== Getting Going ===

Work in progress!

==== Backing up the existing Android installation with dd ====

We only actually alter the kernel, so this is the only one you need to backup, but you may as well do the whole lot just in case. Note that you need to "root" your Tab to be able to use these commands. Also note that this assumes you know how to use adb.

From here: http://forum.xda-developers.com/showthread.php?t=850359

Chose a location to create the backups, e.g. /sdcard

mkdir backup
cd backup
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
adb shell su -c "tar -czvf /sdcard/data.tar.gz /data"

adb pull /sdcard/param.lfs .
adb pull /sdcard/zImage .
adb pull /sdcard/factoryfs.rfs .
adb pull /sdcard/dbdata.rfs .
adb pull /sdcard/cache.rfs .
adb pull /sdcard/modem.bin .
adb pull /sdcard/efs.rfs .
adb pull /sdcard/boot.bin .
adb pull /sdcard/Sbl.bin .
adb pull /sdcard/pit.pit .
adb pull /sdcard/data.tar.gz .

==== Kernel Compilation ====

Grab the kernel source code from http://opensource.samsung.com/
Follow: Mobile > Mobile Phone > GT-P1000 > GT-P1000_OpenSource.zip. There is a new GT-P1000_OpenSource_Update1.zip but I've not tried that, please do tell if it works or works better ;)

----
[GERO@LIKEMAG] Please note that the GT-P1000_OpenSource_Update1.zip has been updated at least '''twice''' on the Samsung server. I got the newest version today. They included some more drivers and fixed some minor bugs '''but removed the TinyFSR config option (by accident?)''' - You have to manually modify Kbuild and Makefile in drivers to get TinyFSR!!!
----

* Link to kernel source (http://opensource.samsung.com/ search for "gt-p1000", select "GT-P1000_OpenSource.zip")

Extract the source, follow the instructions in the readme.txt to grab the cross-compiler and edit the relevant settings in the build_kernel.sh script.

* Link to cross-toolchain (http://www.codesourcery.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2)

Note that we use the same source and toolchain so that the PVR kernel modules will still work (as we're dual booting Android)

* patches to kernel defconfig (defconfig here: http://people.bath.ac.uk/enpsgp/Tab/kernel/)
* Patches to kernel to combine bootloader cmdline and compile-time cmdline (modified setup.c here, also needs some more patches to other files, add these: http://people.bath.ac.uk/enpsgp/Tab/kernel/)

Try compiling to see if it all works. It should do. If you get the following warning "WARNING: modpost: Found 13 section mismatch(es).", don't worry, that appears to be normal (!)

Note that we could try enabling kexec if we find that keeping compatibility with the Android kernel is too limiting and then kexec away to our less constrained kernel. Need to test this.

* link to scripts to extract and rebuild initramfs (http://people.bath.ac.uk/enpsgp/Tab/initramfs/)

==== Pre-built kernel ====

* link to zImage - for those who don't want to do any building (http://people.bath.ac.uk/enpsgp/Tab/kernel/zImage)

==== Flashing the kernel ====

* instructions for flashing kernel using heimdall (install heimdall: http://www.glassechidna.com.au/products/heimdall/ then: "heimdall flash --kernel zImage")

==== Building the Meego rootfs image ====

* link to kickstart file (http://people.bath.ac.uk/enpsgp/Tab/)

Add note about "extras" - modules are in initramfs, so just extract these and add to the image; wifi firmware and other files are in the Android install. We could extract these at runtime, but currently are setup for them to be pre-extracted and added to the Meego partition. Make some notes about location of these files and alternative methods of extracting at runtime.

* instructions for creating image and sticking that on a uSD card (same as N900 instructions)
(sudo mic-image-creator --run-mode=0 --cache=/home/simon/development/meego/build/mycachedir/ --format=raw --arch=armv7l --config=./meego-handset-armv7l-galaxy-tab-1.1.80.15.20110118.5.ks)

=== Setup notes ===

* Getting wifi up and running

* Using adb with Android to extract files from the live Android system (if required)

=== Useful things to look into ===

* How to decide whether to boot Android or Meego - work out how the Android init determines the boot mode (not a kernel command line param nor an argument passed to init, so presumably some /dev or /proc entry information?)

* Galaxy Tab keyboard scan codes - while the kb dock works, ctrl-c is non-functional, it does not have an escape key and there is no cursor displayed (makes vi editing fun ;))

=== Nb ===

* Android will not start up unless you pass the standard bootloader cmdline arguments to the kernel, so if you want to add more arguments you need to either combine them or reproduce them at compile time. Either way you need a kernel patch as otherwise the bootloader cmdline overrides and replaces whatever you specified at compile-time.
* While adding console=tty0 to the kernel command line means you see the boot-time output, it prevents the Tab kb dock from functioning! This is because the P1 keyboard driver measures the boot time in jiffies. If the time difference is either below or above a specific threshold, then it is assumed that the keyboard dock is there/not there :-) You have to modify the threshold because an activated console consumes more time during the boot process.

== Ubuntu ==
===Current Status===

Working:

* Boot Ubuntu (ext4 partition off the internal or external SD Card).
* WIFI ( SSH in for interactivity).
* GPIO hardware power button (So you can do a proper shutdown).
* FrameBuffer (Display an XServer).
* Touchscreen.

Partial Working:

*USB - Does not show up as a device attached to your computer, but does charge.
*Audio - Output can be attained, but is not scanned by pulseaudio and is not set and forget.

Not Working:

* Bluetooth (no idea here, just doesn't detect a bluetooth device even with the module loaded).
* Cellular Data - This will require the reimplementation of librild to interface with onedram mailbox, post the firmware and nvram and toggle the baseband boot gpio.
* Buttons along the bottom (They detect input but they aren't mapped to do anything).

Not Yet Tested:

* Everything else.

===Setup Instructions===

====Root FileSystem====

The 2 options for RootFS are Download a prebuilt image or generate your own.

=====Generate your own rootfs=====

Prerequisites:

# Ubuntu install that has internet access (can be in a VM).
# A little bit of command line knowledge.
# Rootstock (can be obtained through aptitude).
# Some time.

=====Creating your Image=====

# Elevate your terminal to root permissions (sudo -s).
# Install rootstock if you haven't already done so (apt-get install rootstock -y).
# Run rootstock with the following syntax (you may change the hostname/default user/pass as they are not essential to following these directions)
#:<code>rootstock --fqdn GalaxyTab --login ubuntu --password ubuntu --imagesize 5G --seed netbook-launcher-efl,onboard,ubuntu-netbook-efl-default-settings,wicd,wicd-curses,wicd-cli</code>
##You will need to add gdm, xorg and openssh-server to the list above. Can someone confirm. --lardman
# Have a coffee and hope it builds.

After following these steps you will have your own generated rootfs.tgz ready to be extracted in to your Galaxy tab, A pre-prepared image will be available for download soon.

Before Continuing any further please follow the steps provided above in the tutorial above about backing up your system, The install process is destructive to /data so backing it up if you want to go back to android is a good idea.

====Install image to your device====

=====Install to internal SD card=====

This step is done in recovery and requires running some commands via ADB, if you are not comfortable with this DO NOT PROCEED.
This part of the install will have a script to help the install some time in the future.

# Boot into recovery.
# Mount /system, and make sure that /Data is not mounted.
# Make sure you have backed up your android install before going any further.
#* If you are installing to internal SD replace $SD with "mmcblk0" and $P with p3 in the following instructions.
#* If you are installing to external SD replace $SD with "mmcblk1" and $P with p1 in the following instructions.
# Run "parted /dev/block/$SD" and delete all partitions (this is why you made a backup).
# Create new partitions and do mkfs after creation to the following specifications.
#*Internal SD; 3 partitions, Partition 1 type vfat and size of your choice(this is internal SD in android and /media/SD in ubuntu if you set up the SD mount); Partition 2 type vfat and size of 1.5GB (you will restore the data backup to here); Partition 3 type ext2 and rest of disk (this is ubuntu install so make sure you leave enough room).
#* External SD; 1 or 2 Partitions, Partition 1 ext2 as big as you want your ubuntu partition to be; Partition 2 vfat if there is any space left unpartitioned to be used as a normal SD card.
# Run "tune2fs –O dir_index,uninit_bg,has_journal $SD$P"
# Run "e2fsck -pf /dev/block/$SD$P"
# Run "mount /dev/block/$SD$P /sdcard"
# Use adb to push rootfs.tgz to /sdcard as rootfs.tar.gz (eg: adb push rootfs.tgz /sdcard/root.tar.gz).
# Run "gunzip rootfs.tar.gz && tar xvf rootfs.tar"
# Put all the modules (some will need to come from make modules from the kernel some can come from your android image) and wifi firmware & nvram (located in /system/etc/wifi) in their appropriate places.
# In a chroot environment run "moddep -v && update-initramfs -c -v -k 2.6.32.9"
# Add the rootfs to fstab.
# Add mtev touch screen driver and udev rule.
# Pull initramfs from /sdcard/boot as you will need that for the kernel.

=====Install to external SD card=====

# Format your uSD card in your desktop Linux box using (ADD COMMAND, ADD NOTE ON SUPPORTED FORMATS - ext4 works for certain)
# If you don't have a Linux box, you can use a LiveCD, or format using the Tab itself (ADD INSTRUCTIONS)
# Extract the rootfs.tar.gz (generated by rootstock above) to your pre-formatted SD card
# Put all the modules (some will need to come from make modules from the kernel some can come from your android image) and wifi firmware & nvram (located in /system/etc/wifi) in their appropriate places. (ADD SOME MORE DETAIL ABOUT HOW TO EXTRACT THESE)
# In a chroot environment run "moddep -v && update-initramfs -c -v -k 2.6.32.9" (ADD DETAIL ABOUT CHROOT'ing AND WHAT YOU NEED INSTALLED)
# Add the rootfs to fstab.
# Add mtev touch screen driver and udev rule. (THIS WILL PROBABLY BE CHANGED NOW WITH THE NEW DRIVER)
# Pull initramfs from /sdcard/boot as you will need that for the kernel. (CUSTOM INITRAMFS MAY BE REQUIRED FOR EXTERNAL SD, NEED TO CHECK)

Adding more info today as I do a new build (to help me remember the steps!) - lardman 9th April 2011

====Preparing the kernel====

This assumes that you have experience building your own kernel.

# Find and apply Lardmans kernel command line patch.
# Patch s3cfb_lms700jf.c to prevent LCD poweroffs (I couldn't find the right place to do the sysfs tweak I outlined above for the Meego install so looks like kernel patch is the way for Ubuntu --lardman)
# Edit the kernel config to allow udev to work (set CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y).
# edit the console command line.
#* For verbose boot "console=tty0". (recommended to see what's going on)
#* For an install to internal SD Card add "root=/dev/mmcblk0p3"
#* For an install to external SD Card add "root=/dev/mmcblk1p1"
# Extract initramfs you generated in the chroot above. (we should just give a direct download of this)
# Set extracted initramfs as initramfs in kernel config.
# Compile and flash kernel.

These instructions are by no means complete at this time, more concise instructions will come soon, as well as prebuilt images to make installation slightly easier (Prebuilt combined with install scripts should be easier than all of this ever could be)

= Related Wiki Pages =

[[ARM/MSMQSD| MeeGo on ARM/Snapdragon (MSM/QSD)]]

= Team members =

* Steven Troughton-Smith / steventroughtonsmith - Nexus S & ??
* Simon Pickering / lardman - Galaxy Tab (Meego)
* lilstevie - Galaxy Tab (Ubuntu) & ??
* cb22 - Galaxy Tab

[[Category:Hardware]]

Quality/QA-tools

2011-04-07T15:08:26Z

Asinnela: /* Overview */ Test automation concept video linked

= Quality assurance (QA) tools =

''' We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there. '''

[[File:Tool_meegon.png|400px]]

Quality Assurance tools are developed to ensure MeeGo SW quality. QA tools team develops and maintains tools for quality assurance.

* "Open source tools – available for all, available for development and contributions. Make people accountable for quality."

'''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|QA tools development]] page. We apologize for any inconvenience. The target is to make this page clearer and more informative for the actual users of QA tools.

== Overview ==

QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the figure below. In addition, there are also a couple of concept videos available at our [http://www.youtube.com/user/meegoqatools YouTube channel]:
* [http://www.youtube.com/watch?v=WdXBqGdLz8I Tool offering for manual testing]
* [http://youtu.be/Ry4MM-CX2b8 Test automation]

[[File:Meego-qa-tools.png|600px]]

== Tools, test suites and other utilities ==

If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]].

'''Test tools'''

Each wiki page will contain more detailed description, installation instructions and tutorial on the basic usage. For now, please [[Quality/QA-tools#Collaboration spaces|contact us]] if you need help. Currently, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, Meego-ai, libcqpid, eat and MIN from Tools:Testing repository. The instructions for setting up the repositories can be found [[Quality/QA-tools/How_to_set_up_repositories|here]].

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device tool for sending core dumps to core dump data base
|-
| [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] ||
|-
| [http://min.sf.net/ MIN Test Framework] || Advanced test framework
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testplanner|Testplanner]] || Simple tool for creating and editing test plan files
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/Testrunner|Testrunner]] || Test execution tool with graphical UI
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|}

'''Test suites'''

{| border="1" cellspacing="0"
|+
|'''Test suite (link to wiki page)''' ||| '''Test plans'''
|-
| [[Quality/TestSuite/MCTS|MeeGo Core Test Suite]] ||[http://testplans.meego.com/mcts/ Link]
|-
| [[Quality/TestSuite/handset-test-suite/handset-ux-test_Releases |MeeGo Handset UX Test Suite]] ||[http://testplans.meego.com/handset-ux-tests/ Link]
|-
| [[Quality/Netbook Test Suite and Utilities|MeeGo Netbook Test Suite]] ||[http://testplans.meego.com/mnts/ Link]
|-
| MeeGo SDK Test Suite ||[http://testplans.meego.com/meego-sdk-tests/ Link]
|}

'''Other utilities'''

{| border="1" cellspacing="0"
|+
|'''Name (link to wiki page)''' ||'''Short description'''
|-
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||
|-
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] ||
|-
| Rich Core dumper ||
|-
| Crash Reporter settings || Settings package for Crash Reporter
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] ||
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] ||
|-
| Service OS based Flasher ||
|-
| [[Quality/QA-tools/Qpid C wrapper|Qpid C wrapper library - libcqpid]] ||
|}

== Feature requests and bugs ==

Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=ASSIGNED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance Assigned bugs and features - Working on it]
* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order]

Bugzilla instructions:
* [[Quality/How To Report Bugs|How to report bugs]]
* [[Quality/Bug Life Cycle and Handling|Bugzilla workflow]]

== Collaboration spaces ==

Team communication is in English. Our collaboration spaces are:
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net]
* [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos]
* [http://meegoqatools.wordpress.com/ QA-tools team blog]

[[Category:QA]]

ARM/N900/DeveloperEdition

2011-04-05T13:03:18Z

Asinnela: /* FAQ */ wiki link fix

= MeeGo 1.2 Developer Edition for N900 =

== Target ==

Target is to make a Developer Edition of MeeGo for the Nokia N900 device. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This will not be something for regular end users'''.

The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 trunk content. MeeGo features are found in [https://bugs.meego.com/ bugzilla].

You can join the development and discussion at the [http://lists.meego.com/listinfo/meego-handset meego-handset mailing list] and in IRC (#meego-arm @freenode).

== Use cases (do not edit these directly, instead add feedback to the bottom of page) ==

These use cases shall be the prominent ones in the device Home screen. In addition there will be separate folder containing other available Handset apps from repositories, and there is a possibility to promote any app to the main view if the non-functional targets are met.

'''Voice calls''' (Dialer, People)
* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it's MeeGo 1.2 compliant.

== Organization ==

* Core team is being formed in and around Nokia.
* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/essi Essi Vehmersalo]
*** [[ARM/N900/Browser|Browser and Wlan]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen], including current [[ARM/N900|N900 HW adaptation team]].
*** Architect: [http://meego.com/users/mythi Mikko Ylinen]
*** Release & integration: [http://meego.com/users/kad Alexander Kanevskiy], [http://meego.com/users/ericlr Eric Le Roux]
** [[ARM/N900/QA|QA]] lead: [http://meego.com/users/jkunnari Jake Kunnari]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

* Community involvement is very desirable, and there will lots of areas to contribute (see below).

== Schedule ==

* Alpha release: on week 15
* Beta release: on week 20 (MeeGo Conference)
* Final release candidate: on week 25

The criteria and content for the milestones will be defined further, but this is just to show our '''target schedule'''.

== Status ==

See the [[ARM/N900/Status|Status]] page for reports.

== Meetings ==

* Work space in IRC (@freenode, #meego-arm) and regular MeeGo mail lists (primarily we will be using [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com].
* [[ARM/N900/DeveloperEdition/Meetings|Weekly team meetings]] are held in the public IRC. The agenda and the archives are also available. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]].

== Installing and running ==

* N900 Handset images: [http://repo.meego.com/MeeGo/builds/trunk/latest/ weekly build], [http://download.meego.com/trunk-daily/builds/trunk/latest/ Trunk-daily], [http://download.meego.com/testing-daily/builds/trunk/latest/ Trunk-Testing]
** See the [[Release Engineering/Repo List|release engineering repository list]] for explanation of different images.
** '''Before installing please read about the recommended method: [[ARM/N900/Install/Dual_Boot|dual boot installation]]'''. That way you can keep Maemo on the device at same time.
* Developer Edition images: Coming soon, see [[ARM/N900/ReleaseProcess]]. PM recommends to try with current [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 Acceptance images]. Check the test results, and if they look good you can find the image name in the report.
* [[ARM/N900/Install/MMC#Installing_Rootfs_on_external_MMC_card|Flashing instructions]] (when using dual boot method, no need to flash/load the kernel separately).
* Tips and tricks (please add yours here!)
** Connect to WLAN: Settings->Applications->WiFiApplet
* There is also some more [[ARM/N900/CoolStuff|Cool stuff]] to try on top of the MeeGo image.

== I want to help! ==

Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material]] gives the overview on the daily development workflow. Thanks Fathi Boudra & Markus Lehtonen for the contribution. Also any suggestion where to locate the links to this material is appreciated.

Some more concrete steps:

* Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
* Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
* Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
* Look into learning QML if you haven't already.
* Would like to contribute the test cases? You will find the useful information [[Quality|here]].
* Would like to contribute artwork? See [[ARM/N900/Artwork]].

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but not in the official 1.2. What do we do with the bug? 
A. Remove the DE_Blocker flag from the official bug. Comment that the fix is available in DE. Try to contribute the fix to 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. This is work in progress. See the [[ARM/N900/ReleaseProcess|release process]] explained by Carsten.

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new Tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

[[File:Splash-developers.png]]

[[Category:N900]]

Quality/QA-tools/User experience

2011-04-04T05:30:20Z

Asinnela: /* Proposal for Future Work */

= MeeGo QA tools user experience =

This is the main page for user experience (UX) work done for MeeGo QA tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-users and their input are crucial. By understanding the users and their needs, it is possible to develop something that really benefits the users.

This page is meant for giving an overview of UX activities regarding QA tools. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla.

== UX Workflow in a Nutshell==

User experience is not something that could just be added to a product as the last thing of the implementation process. On the contrary, user experience work focuses on taking the users into account in every phase of the development process. The following gives just one example on how you can do user-centered design in practice:

# Identify who are the actual and/or potential users
# Conduct a user study and identify the users' needs and wishes
# Draft and iterate e.g. a paper prototype of the planned UI with the users
# Based on the iterated prototype and other input, design and implement a functional prototype
# Present the functional prototype to the users as early as possible and gather feedback and improvement ideas. You can also conduct a more formal usability study.
# Re-design and continue implementation
# Once the first complete version is released, continue to gather user feedback and implement improvements

Meeting users face-to-face is preferred but online methods can also be used. E.g. the input can be gathered via mailing lists or IRC, and design drafts can be published to wiki or Bugzilla.

== Ongoing Work==

* Every Tool
** Check the end-user documentation

== Proposal for Future Work ==

* Every Tool
** Evaluate the ease of the installation and the first time use
** Improve visual look of the GUI tools, e.g. improve icons and other graphical elements
* MeeGo N900 DE
** UX evaluation / study
** [[ARM/N900/TabletUX]]

== How to Participate ==

The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are:
* [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net] for discussing about the tools and QA processes in general
* [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Bugzilla] for reporting enhancement ideas or usability problems

Quality/CoreTestReports/MTFTestReports/mcpandapplets

2011-04-01T12:29:17Z

Asinnela: Wiki link fixes

{| align="right"
| __TOC__
|}
 

Repository: ''Trunk-testing & devel:qt-mtf'', Device : n900
== meegotouch-controlpanel ==



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.12.1.2''' [http://af09.nrln.net/gabor/20110308_mcp-config.txt Config] 08.03.2011
|| [http://af09.nrln.net/gabor/20110308_mcp-results.txt Unit Tests] || 25 || 24 || 1 || 0 || Fixing in the next release
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.11.5.1''' [[Media:20110216_Mcp-config.txt|Config]] 16.02.2011
|| [[Media:20110216_Mcp-tests-results.txt|Unit Tests]] || 25 || 25 || 0 || 0 ||
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.11.2.1''' [[Media:20100117_Config_mcp.txt|Config]] 17.01.2011
|| [[Media:20100117_Duicontrolpanel-tests-results.txt|Unit Tests]] || 25 || 25 || 0 || 0 ||
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.9.8.1''' [[Media:Meego-handset-armv7l-n900-systemsettings-test-20101210-1.1.80.20101210.0006-pkgs.txt|Config]] 10.12.2010
|| [[Media:20101210Meegotouch-controlpanel-test-results.xml|Unit Tests]] || 29 || 29 || 0 || 0 ||
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}

== meegotouchcp-datetime ==



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.7.50.1''' [http://af09.nrln.net/gabor/20110401-meegotouchcp-datetime-config.txt Config] 01.04.2011
|| [http://af09.nrln.net/gabor/20110401-meegotouchcp-datetime-test-result.txt Unit Tests] || 7 || 7 || 0 || 0 || BMC_14277_Time-view-does-not-follow-time-view-setting.patch
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.7.50.1''' [http://af09.nrln.net/gabor/20110308_datetime-config.txt Config] 08.03.2011
|| [http://af09.nrln.net/gabor/20110308_mcp-results.txt Unit Tests] || 7 || 7 || 0 || 0 ||
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.7.43.6''' [[Media:20100119_Config.txt|Config]] 19.01.2011
|| [[Media:20100119_Datetime_results.txt|Unit Tests]] || 7 || 5 || 2 || 0 || The qmsystem-1.0.0 is buggy BMC#12641. Date&Time can be set most of the times (90%) . Time zone can't be set. Unit tests will be fixed in the next release.
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
|}

== meegotouchcp-language ==



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.8.24''' [[Media:20110217Lang-config.txt|Config]] 17.02.2011
|| [[Media:20110217Lang-result.txt|Unit Tests]] || 7 || 7 || 0 || 0 || -
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.8.16''' [[Media:20101211Config.txt|Config]] 11.12.2010
|| [[Media:20101211Meegotouchcp-language-test-results.txt|Unit Tests]] || 7 || 7 || 0 || 0 || -
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.8.12''' [[Media:20101118Pkgs.txt|Config]] 18.11.2010
|| [[Media:20101118Displaylanguageapplet-test-results.xml|Unit Tests]] || 7 || 5 || 2 || 0 || Fixing in the next release
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.8.6''' [[Media:Meego-handset-armv7l-n900-develqtmtf-test-20101028-1.1.80.20101028.0034-pkgs.txt|Config]] 22.10.2010
|| [[Media:20101028Duicontrolpanel-displaylanguageapplet-tests-results.xml|Unit Tests]] || 5 || 4 || 1 || 0 || -
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}

== meegotouchcp-regionformat ==



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.2.32.2''' [[Media:20110301Region-config.txt|Config]] 01.03.2011
||[[Media:20110301_Regionformat-results.txt|Unit Tests]] ||10 ||10|| 0||0 ||-
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.2.29.2''' [[Media:20110118_Region_config.txt|Config]] 18.01.2011
||[[Media:20110118_Duicontrolpanel-regionformatapplet-tests-restuls.txt|Unit Tests]] ||10 ||10|| 0||0 ||-
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.2.28''' [[Media:20101211Config.txt|Config]] 11.12.2010
||[[Media:20101210Meegotouchcp-regionformat-test-results.txt|Unit Tests]] ||10 ||10|| 0||0 ||-
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center"|'''0.2.24''' [[Media:20101203Pkconfig.txt|Config]] 03.12.2010
||[[Media:20101203_Meegotouchcp-regionformat-test-results.xml|Unit Tests]] ||10 ||10|| 0||0 ||-
!style="background:#DDFFDD" |Yes
|-
|| Acceptance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests ||-||-||-||-||-
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
|}

== meegotouchcontrolpanel-applets ==

{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.20.17''' [[Media:Meego-meego_handset_2011_03_02_with_mcp_applets-1.1.90.20110302.1343-pkgs.txt|Config]] 04.03.2011
|| [[Media:Test_2011_03_01_17_02.xml|Unit Tests]] ||55 || 52|| 3|| 0 || Fixing in the next release
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || || || || ||
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || || || || ||
!style="background:#FFDDDD" |No Release
|- style="border-witdh:0px" border=0
!colspan="10" |
|}

== template ==

{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''Version''' [http://config Config] Date
|| Unit Tests || || || || ||
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || || || || ||
!style="background:#DDFFDD" |Yes
|-
|| Performance Tests || || || || ||
!style="background:#FFDDDD" |Refused
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center" |'''Version''' [http://config Config] Date
|| Unit Tests || || || || ||
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || || || || ||
!style="background:#DDFFDD" |Yes
|-
|| Performance Tests || || || || ||
!style="background:#FFDDDD" |Refused
|}

Quality/CoreTestReports/ContentFWTestReports

2011-04-01T07:07:41Z

Asinnela:

ContentFW test reports

== References ==

* Test Image: meego-handset-armv7l-n900-contentfwf-test-20101214-1.1.80.20101214.0117-mmcblk0p.raw
* Kernel version: 2.6.35.3-18.3-n900
* Hardware: N900

= libcontentaction =



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.1.39''' Config 07.12.2010
|| [l Unit Tests] || 12 || 11 || 1 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.1.35''' Config 07.12.2010
|| [[Media:Libcontentaction-results-0.1.35.xml|Unit Tests]] || 12 || 11 || 1 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}

= libqttracker =
* Test Image: meego-handset-ia32-nCDK-daily-1.1.80.20110111.0924.fiasco
* Kernel version: 2.6.35.3-18.3-n900
* Hardware: NCDK EB3



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''6.12.6''' Config 13.12.2010
|| [[Media:Results-libqttracker-6.12.4.xml|Unit Tests]] || 124 || 124 || 0 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''6.12.1''' Config 07.11.2010
|| [[Media:Results.xml|Unit Tests]] || 124 || 117 || 7 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''6.12.4''' Config 13.12.2010
|| [[Media:Results-libqttracker-6.12.4.xml|Unit Tests]] || 124 || 120 || 4 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}

= tracker =

* Test Image: meego-handset-ia32-nCDK-daily-1.1.80.20110111.0924.fiasco
* Kernel version: 2.6.35.3-18.3-n900
* Hardware: NCDK EB3



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.9.30''' Config 04.01.2010
|| [[Media:Tracker-0.9.29.results.xml|Functional Tests]] || 42 || 36 || 6 || 0 || Failed test cases are: 400-extractor.py(video extraction test cases are failed), 310-fts-indexing.py, 200-backup-restore.py
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.9.29''' Config 13.11.2010
|| [[Media:Tracker-0.9.29.results.xml|Functional Tests]] || 40 || 35 || 5 || 0 ||
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.9.26''' Config 07.11.2010
|| [[Media:Tracker-0.9.25results.xml|Functional Tests]] || 32 || 29 || 3 || 0 ||Failed test cases are: 400-extractor.py(video extraction test cases are failed),11-sqlite-batch-misused.py, 12-transactions.py fail due to timeout error.
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}



{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''0.9.25''' Config 26.10.2010
|| [[Media:Tracker-0.9.25results.xml|Functional Tests]] || 32 || 27 || 5 || 0 ||Failed test cases are: 400-extractor.py(disabled tracker-extract while compiling because of compilation errors),11-sqlite-batch-misused.py, 200-backuprestore.py, 13-threadedstore.py, 12-transactions.py fail due to timeout error.
!style="background:#FFDDDD" |No Release
|-
|| Acceptance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|-
|| Performance Tests || - || - || - || - || -
!style="background:#FFDDDD" |No Release
|}

== template ==

{| style="background:#f9f9f9;border:1px #aaaaaa solid;border-collapse:collapse;width:100%;font-size:11pt;" border=1 cellpadding="1" cellspacing="0"
|- style="background:#E6E6FA;text-align:center;font-size:12pt"
!Release !!Test Result !!Test Suites !!Passed !!Failed !!Skipped !!Comments !!Integrated
|-
|rowspan="3" align="center"|'''Version''' [http://config Config] Date
|| Unit Tests || || || || ||
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || || || || ||
!style="background:#DDFFDD" |Yes
|-
|| Performance Tests || || || || ||
!style="background:#FFDDDD" |Refused
|- style="border-witdh:0px" border=0
!colspan="10" |
|-
|rowspan="3" align="center" |'''Version''' [http://config Config] Date
|| Unit Tests || || || || ||
!style="background:#FFFFD0" |Pending
|-
|| Acceptance Tests || || || || ||
!style="background:#DDFFDD" |Yes
|-
|| Performance Tests || || || || ||
!style="background:#FFDDDD" |Refused
|}

Quality/Compliance

2011-04-01T06:56:58Z

Asinnela: /* Specification */

= MeeGo Compliance =

The MeeGo compliance program is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software, and so that app developers know how to build software which will run across the family. Simply put, we want to make it possible for an application developer to write a MeeGo compliant application once and run it on any MeeGo compliant device.

MeeGo compliance addresses two categories of compliance: MeeGo compliant applications and MeeGo compliant devices / software products (which will be referred to simply as "devices"). In both cases, the use of the MeeGo brand will be granted based on being compliant. Following is an overview of the approach for each of these categories.

==MeeGo Compliant Device Overview==

For MeeGo compliant devices, we're taking a stack-based compliance approach, meaning that all MeeGo devices must use the same core software stack. Referring to the MeeGo architecture diagram, this core software stack is the MeeGo OS base layer plus the MeeGo OS Middleware layer.

In addition to a sharing the same core software stack, MeeGo compliance will have profiles for each device category (Netbook, Handset, and so on). A profile specifies additional required components for the profile (e.g. providing device category APIs), minimum hardware requirements and minimum hardware component requirements (such as cellular modem in the handset profile).

It's important to note that the device profiles won't require the inclusion of a complete user experience - but rather the UI framework providing core user interaction and APIs.

A MeeGo compliant device would be compliant to the MeeGo core software stack definition and one (or more) device category profiles.

==MeeGo Compliant Application Overview==

Given that definition of compliance for devices / software products, MeeGo compliance for applications will verify that an application's external dependencies are satisfied by a MeeGo compliant device (in other words, that any libraries or other dependencies of the application are provided within the core software stack and target device profile)

An application can be written to be dependent only on the MeeGo core software stack - in which case it would run on any MeeGo compliant device. However, applications with UI would typically target a specific device profile - so for example an application could be MeeGo Handset Compliant - meaning that it would run on any device compliant with the MeeGo Handset profile.

==More Detail on Stack Based Compliance==

Stack-based compliance means that a compliant device / software product must use the MeeGo package set without re-packaging - including the MeeGo version of RPM and the MeeGo package names.

Compliance requires the use of the MeeGo source packages for required components, and that any applied patches (e.g. to fix bugs found in the field) must not effect API, ABI, or defined functionality of interfaces.

Additional packages (beyond those required by compliance) may be added as long as they don't override MeeGo packages or provide functions with the same namespace of MeeGo APIs. Of course there will also be additional packages and components required to adapt MeeGo to run on a specific hardware platform (we call this "Hardware Adaptation Software" in MeeGo) - the compliance specification will call out any specific packages or components that may vary based on hardware capabilities.

A core part of the program is the Compliance Specification, which describes the rules and requirements for complying. There's more to the program (trademark licensing, application process, etc.) which will be added later.

== Specification ==

The specification is intended to match up with MeeGo releases, so it uses a similar numbering scheme.

Current drafts:

* [[Media:MeeGo-Compliance-Spec-1.0.99.7x.pdf|Spec 1.0.99.7]] - for Feb 9 2011 TSG meeting
** Earlier [[Media:MeeGo-Compliance-Spec-1.0.99.5.pdf|Spec 1.0.99.5]] | [[Media:MeeGo-Compliance-Spec-1.0.99.4.pdf|Spec 1.0.99.4]] | [[Media:MeeGo-Compliance-Spec-1.0.99.3.pdf|Spec 1.0.99.3]] | [[Media:MeeGo-Compliance-Spec-1.0.99.2.pdf|Spec 1.0.99.2]] | [[Media:MeeGo-Compliance-Spec-1.0.99.1.pdf|Spec 1.0.99.1]]

Initial public draft for comment.

* [[Media:MeeGo-Compliance-Spec-1.0.80.8.pdf|Spec 1.0.80.8]]

For now, comments to the meego-dev mailing list, until we get kicked off!

Work in progress:

* [[Quality/Compliance/HandsetProfile|Handset Profile]]

== Compliance Tools ==

The Compliance Tools are used to check compliance for MeeGo Distributions or MeeGo Applications. The reference input is the MeeGo core package/file list and a minimal MeeGo reference image created by MIC2, which will contain all the required core packages, as well as source rpms.

For MeeGo distribution compliance checking, the input needs to include the OS image and the source rpms for all the packages.

For MeeGo Application compliance checking, the input is the application rpm file.

See [[Quality/ComplianceTools|ComplianceTools]] for details.

== Schedule MeeGo 1.1 Compliance ==

* Preliminary compliance package list (i.e. the minimum set of required on-device packages) - DONE
* Next Rev of compliance spec including profiles - DONE
* First version of compliance tools for distribution / device - DONE
* First version of compliance tools for applications - DONE
* Final compliance package list and spec for 1.1 release, and tools updates as needed - with the MeeGo 1.1 release end of October

== Meego Conference 2010 session ==

At the Meego Conference 2010, Mark Skarpness gave a talk on this subject.

http://conference2010.meego.com/session/app-compatibility-and-meego-compliance-program

Quality/Bugzilla Fields

2011-04-01T06:44:56Z

Asinnela: /* MeeGo Release */

=Bugzilla Fields=
==MeeGo Release==

MeeGo Release field defines in which MeeGo version a bug has been found.
Version names are defined according to the [[Release_Engineering/Plans|MeeGo release plan]]. If a bug was reported already for an older MeeGo version make sure to [[Quality/defects#Bug Cleanup after Project Release|handle this bug as described here]].

==Target Milestone==

When bugs are in OPEN status, the Target Milestone is used by an experienced bug reporter or by a developer to propose for which future MeeGo release this bug should get fixed.
When bugs are in RESOLVED status,the Target Milestone is used to describe in which (existing or upcoming) MeeGo release this bug is fixed.

==Importance==
===Priority===

Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. A bug triage team sets the initial priority for the bug, which might be changed. Priorities range from High (most important) to Low (least important).
* High: Bug fixing is on-going, or is planned within 2 weeks, no later than the up-coming milestone. Reproducible crash issues, major function loss, issues greatly impact user experience or issues which block other key features to work would fall in to this category.
* Medium: Bug fixing is planned before project release, but can't start before HIGH priority items are cleaned up.
* Low: Bug fixing is not planned for the up-coming project release. Will re-evaluate the importance in next release.

===Severity===

The "Severity" field describes the impact of an issue. The options include:

* Critical: crashes, other components are affected
* Major: major loss of own function
* Normal: regular issue, some loss of functionality under specific circumstances
* Trival:cosmetic problem like misspelled words or misaligned text
* Enhancement: request for enhancement

==Platform==
===Hardware===

The UX (like Netbook, Nettop, Notebook, Handset, Automotive, TV) the issue has been identified in.
For bugs which apply to all UX (like bugs for Middleware/Core components), there is "All".

===Architecture===

The architecture (like [http://en.wikipedia.org/wiki/Intel_Atom IA], [http://en.wikipedia.org/wiki/ARM_architecture ARM]) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA.
For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".

==Keywords==

[https://bugs.meego.com/describekeywords.cgi Keywords] can be added to reports to quickly find issues of the same keyword category across various products and components.

{|
| style="background: #ffcc00; color: black" | '''TODO:''' Define process how to introduce/announce/decide on addition/deletion of keywords. -- [[User:Andre]]
|}

=See Also=
* [[Quality/Bugtriage|MeeGo Bug Triage]]
* [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[Quality/How_To_Report_Bugs|How to report bugs]]

Quality/Bugtriage Tasks

2011-04-01T06:44:22Z

Asinnela:

[[Quality/Bugtriage_Guide|← Go back to the Triage Guide]]

There are a number of ways to start triaging. If you have more ideas feel free to add them here.

==Triage a single application==
Pick up the product or component that interest you, or which you know about, or are willing to learn, or happen to use. You can [https://bugs.meego.com/query.cgi?format=advanced query] for existing open reports and take a look at issues that interest you, for example in order to update them by updating the Version field, or noting that they have been already fixed in the version you use (please mention the exact version that you use in a comment). If you want to constantly be informed about any changes, set up user watching by adding the [https://bugs.meego.com/describecomponents.cgi "Default QA Contact"] email address to your [https://bugs.meego.com/userprefs.cgi?tab=email "User Watching"] list. See [http://blogs.gnome.org/aklapper/2008/12/18/watching-products-in-maemoorg-bugzilla/ this blogpost for bugs.maemo.org] for a longer explanation about how this works.

==Triage the latest incoming reports==
Take a look at the latest [https://bugs.meego.com/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=-14d&chfieldto=Now&chfieldvalue=&bug_status=NEW&bug_status=REOPENED incoming reports of the last two weeks] (NEW and REOPENED state) and try to reproduce them, or ask for missing information, or add additional information. See the [http://wiki.meego.com/Quality/Bugtriage_Guide Triage Guide].

==Try to reproduce reports==
Many reported problems cannot be easily reproduced.
[https://bugs.meego.com/buglist.cgi?bug_status=NEW Take a look at bug reports in NEW state], try to reproduce them, and feel free to add a comment either with instructions to reproduce or that you could not reproduce it and mention the version that you use.

==Update reports of older versions==

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Is this information accurate and correct? -- [[User:Andre]]
|}
[https://bugs.meego.com/query.cgi?format=advanced Query] for bug reports with an old MeeGo Release (Version) number and try to reproduce them with the latest software release to find out whether the reports are still valid. If they have been fixed in the meantime, you can add a comment about it.

==Clean up reports that need more information==
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Add link to Stock answers in case we introduce them, and add a "Update the stock answers" section here. -- [[User:Andre]]
|}
Clean up [https://bugs.meego.com/buglist.cgi?bug_status=NEEDINFO&chfieldfrom=-29d&chfieldto=Now reports in NEEDINFO state that have not been changed for four weeks]. This means that more information had been requested from the reporter but has not been provided. These reports should be closed as WORKSFORME if you are not able to reproduce, or as INVALID if there is simply not enough information to be a useful report. Please always explain your decision by adding a friendly comment and in the latter case, ask the reporter to provide the information asked for, if s/he can, and reopen the bug.

Example comment: "Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as WORKSFORME/INVALID. Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this in a recent version."

==Update your own reports==
Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version.
Go to the [https://bugs.meego.com/query.cgi?format=advanced Query website] and make sure that under "Status" NEW, ASSIGNED and REOPENED are checked. Under "Email Addresses, Bug Numbers, and Votes", check the field "the reporter" and enter your email address below in the text field to query for them.

Quality/Plans

2011-04-01T06:40:38Z

Asinnela: /* Plans */

= Plans =

* [[/MeeGo Core Test Plan | MeeGo Core Overall Test Plan]]
* [[/Handset UX test plan|MeeGo HandSet UX Test Plan]] - Generic HandSet UX QA test plan. Valid from MeeGo HandSet UX 1.2 release and onwards.
** [[/Handset UX ramp-up 1.2|QA Ramp-Up Schedule for 1.2]]

* [[/Test-execution | Execution roadmap]]

== Old plans ==

* [[/1.1 Handset UX TestPlan | MeeGo HandSet UX Test Plan]] (for 1.1)
** [[/Handset UX ramp-up 1.1|QA Ramp-Up Schedule]]

* [[Quality/Plans/MeeGo 1.0 Netbook software update|MeeGo 1.0 Netbook software update]]

ARM/N900/QA

2011-04-01T06:28:45Z

Asinnela: /* MeeGo.com IRC meetings */

= QA TODOs (in priority order) =

== MeeGo.com IRC meetings ==

There are no special QA meeting, other DE team meetings can be found from here:
* [[MeeGo-Meeting_IRC_Schedule|MeeGo-Meeting IRC Schedule]]

== OTS setup and automated hourly testing ==

=== OTS setup ===
* [http://194.136.64.78/logger/view/ OTS server] - Ville Ilvonen/Riku Halonen, DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- Ville Ilvonen/Riku Halonen/Timo Harkonen - DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated 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 ==
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS 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.

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de 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 [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (Something goes wrong, when reducer processes coredump.) - NOT STARTED
** Oopslog (and lifelog) functionality - NOT STARTED

* Back-end server
** 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 (Teivas)
* Handset UX weekly testing schedule (Rajala)
{| cellpadding="5" cellspacing="0" border="1"
! 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 [[ARM/N900/DeveloperEdition|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.

== QA Organization ==

== Error Management ==
* Error Manager Iekku Huttunen

== Usefull links ==

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

Proposal for a Quality Assurance working group

2011-04-01T06:27:49Z

Asinnela: Proposing to keep this page as a redirect. There might still be pages outside the wiki linking to this since this was once the official page for QA

#REDIRECT [[Quality]]

Quality/Application developer site/Documentation

2011-04-01T06:12:28Z

Asinnela: Fixed double redirect

#REDIRECT [[Application developer site/Documentation/Features/meego doc]]

SDK/Meetings/20101006 Weekly

2011-04-01T06:07:19Z

Asinnela: /* QA * Jaya * 6:15 - 6:25 */ Removed links to deleted pages

= MeeGo SDK Weekly Meeting 20101006 =

This document contains agenda and minutes of SDK weekly teleconference meeting on 20101006 05:30 GMT.

== Conventions of this document ==

* AP: = Action point agreed on this meeting
* yyyymmdd AP: = Action point agreed on previous meeting
* yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
* yyyymmdd AP DONE: = Action point done
* yyyymmdd AP CANCELLED: = Action point cancelled
* AGREE: = Item that has been agreed by the team
* POSTPONED: = Agenda item postponed from last meeting
* OLD: = Info from previous meeting (delete during the meeting)

== Attendees ==

* Veli Kaksonen, Maurice Kalinowski, Al Nikolov, Fathi Boudra, Jarmo Kant, Ville Lavonius, Bob, Jaya Uppalapati, Titta Väyrynen, Ronan Mac Laverty (-7:55)

== Agenda and minutes ==

* Additions to agenda

=== Project Management & Collaboration * Veli * 5:30 - 5:45 ===

* 20100908 AP: Initiate separate weekly meeting for Releasing (Fathi)
** AP: Invite people from Nokia and Intel (Fathi)
* POSTPONED: Project Plan Review (waiting or requirements)
* 20100929 AP: WRT people to this meeting + subteam (Veli)
* 20100929 AP ONHOLD: Public OBS at OSU -- for community and ISVs (Veli, Bob)

==== MeeGo.com SDK team ====

* Needed roles / responsibilities
** 20100825 AP: Check the proposal (Bob, Kerry).
*** [[SDK/Team Proposal]]
** 20100908 AP: Identify missing areas and owners (Veli, Bob)
*** AP: Quick meeting about this (Veli, Bob)

==== Release cycle ====

* 20100820 AP: Figure out if we can have two week delay in releasing (Veli)
** [[SDK/Two weeks delay proposal]]

=== Product Management ===

* MeeGo 1.2 requirement Status
** 20100929 AP: Put the requirements in wiki (Veli)
*** 20100915 AP: Review the requirements 2nd round (All)
*** Targetted release
** 20100922 AP: Arrange a meeting about these (Veli)
*** 20100818 AP: Agree on requirements (Nokia, Intel)

=== Documentation * Titta * 5:45 - 5:55 ===

* 20100922 AP: Check the existing pages on wiki.meego.com about SDK and find right place for those (Titta)
* AGREE: OBS / OSC instructions are low priority
* AGREE: Testing team will verify installation instructions
* Backlog (requirements) being reviewed by doc team on week 40
** Responsibilities agreed (initial)
* Area owners will take a look what is needed from their areas
* AP Titta and Bob: gather a list of reviewers
* Final approvals: General website: Imad/Valterri. Final: Bob/Veli, right before release
* Risks
** API planning on going (needs to be freeced)
** We need two weeks before release for reviews and testing
** WRT team seems too busy. We need the API docs

=== Releasing & Packaging * Veli * 5:55 - 6:05 ===

* AP: Initial version of Windows installer available this week (John Chen)
* 20100922 AP: Provide windows SDK needed parts (ARM toolchain, QEMU and QEMU image) to John Chen (Al Nikolov)
* 20100929 AP: Draft a wiki page about distribution priorities (Jaya)

==== OBS Integration & Weekly builds * Fathi * ====

* 20100825 AP: Packaging for ISVs. Could leverage public OBS and spectacle (Intel to provide proposal / ideas).
* 20100929 AP DONE: separate maintainer and subsystem maintainer role (Fathi)
** Fill table with the maintainers/subsystem maintainers (All)
* 20100915 AP: Add missing IA32 toolchain (Jackie Wu)
* 20100915 AP: Add missing final ARM toolchain (Fathi, Al)
** work in progress in Al's home under OBS
** bug related to python2.6 (affect gdb only) BMC#
** Ubuntu only packages
** float hard/softfp? (Fathi: look current gcc spec on ARM architecture under MeeGo OBS and do the same)
* 20100820 AP: Kevinwang needs commit rights to ks file gitorious (KevinWang)
** merge request to do

==== Content ====

* MOVE THIS: 20100908 AP: Bob to sync with Veli on Qt Mobility API / impl.
* 20100908 AP: Bob to setup meeting on WRT. Intel people: Bob, Elliot, Kaitlin. Nokia: Ashraf Akarmi, Michael Bierman (PM of tools for WRT), Fathi (integrated WRT into MeeGo).

=== Toolchains * Jarmo * 6:05 - 6:15 ===

* AP: Initiate weekly meetings (Jarmo)
* Change request process draft created
** [[SDK/Toolchains]]
** Austin commented on that

* Generic
** Windows host toolchains
*** Toolchain is building

* ARM target
** 20100929 AP: base ARM toolchain on Kevin's work (Al)
** 20100915 AP: Create a lightweight sysroot for toolchain building (Al)

* Intel x86 target
** 20100908 AP 20100924: Push toolchain packages to dev:tool:sdk:host project (Kevin)

=== QA * Jaya * 6:15 - 6:25 ===

* First test results available
** Please comment

* 20100929 AP: Final test set for MeeGo 1.1 (Jaya)

* 20100820 AP 20100924: How to handle bugfixes of releases (Fathi)
** Create a document about MeeGo SDK related bugs (Fathi)

SDK/Meetings/20100929 Weekly

2011-04-01T06:06:43Z

Asinnela: /* QA * Jaya * 6:15 - 6:25 */ Removed a link to a deleted page

= MeeGo SDK Weekly Meeting 20100929 =

This document contains agenda and minutes of SDK weekly teleconference meeting on 20100929 05:30 GMT.

== Conventions of this document ==

* AP: = Action point agreed on this meeting
* yyyymmdd AP: = Action point agreed on previous meeting
* yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
* yyyymmdd AP DONE: = Action point done
* yyyymmdd AP CANCELLED: = Action point cancelled
* AGREE: = Item that has been agreed by the team
* POSTPONED: = Agenda item postponed from last meeting
* OLD: = Info from previous meeting (delete during the meeting)

== Attendees ==

* Veli Kaksonen, Maurice Kalinowski, Jaya Uppalapati,Fathi Boudra, Cathy Shen,Titta Väyrynen, Ville Lavonius, Bob Spencer, John Chen, Ronan Mac Laverty, Al Nikolov

== Agenda and minutes ==

* Additions to agenda

=== Project Management & Collaboration * Veli * 5:30 - 5:45 ===

* 20100908 AP: Initiate separate weekly meeting for Releasing (?), this is taking too long (Veli, Fathi)
* 20100908 AP DONE: Intel take a look at bugzilla components proposal this week (by 20100910)
** 20100922 AP DONE: Review Kerry comments (Fathi)
** 20100922 AP CANCEL: Merge of QEMU projects (Kerry, Nokia)
* POSTPONED: Project Plan Review (waiting or requirements)
* AP: WRT people to this meeting + subteam (Veli)
* AP: Public OBS at OSU -- for community and ISVs (Veli, Bon)

==== MeeGo.com SDK team ====

* Needed roles / responsibilities
** 20100825 AP: Check the proposal (Bob, Kerry).
*** [[SDK/Team Proposal]]
** 20100908 AP: Identify missing areas and owners (Veli, Bob)

==== Release cycle ====

* 20100820 AP: Figure out if we can have two week delay in releasing (Veli)
** 20100825 AP DONE: Create a proposal wiki-page about the two week delay (Bob)
*** [[SDK/Two weeks delay proposal]]

=== Product Management ===

* MeeGo 1.2 requirement Status
** 20100915 AP DONE: Send the requirents to everyone (Ville)
** AP: Put the requirements in wiki (Veli)
*** 20100915 AP: Review the requirements 2nd round (All)
*** Targetted release
** 20100922 AP: Arrange a meeting about these (Veli)
*** 20100818 AP: Agree on requirements (Nokia, Intel)

=== Documentation * Titta * 5:45 - 5:55 ===

* 20100922 AP DONE: Edit the subteam team page: [[SDK/Documentation]] (Titta)
* 20100901 AP DONE: Extra meeting about documentation (Veli, Titta)
* 20100922 AP: Check the existing pages on wiki.meego.com about SDK and find right place for those (Titta)
* First subteam meeting yesterday
** Responsibilities agreed (initial)
* Area owners will take a look what is needed from their areas
* Risks
** API planning on going (needs to be freeced)
** We need two weeks before release for reviews and testing
** WRT team seems too busy. We need the API docs

=== Releasing & Packaging * Veli * 5:55 - 6:05 ===

* Talk about installation
** Leverage Qt SDK Installer. Intel would like to check it out (John Chen)
** Initial version of Windows installer available this week
** Maurice will help with missing documentation
** 20100922 AP DONE: Provide installer framework info to Intel (Maurice)
** 20100922 AP DONE: Check the installer documentation (Maurice)
* 20100922 AP: Provide windows SDK needed parts (ARM toolchain, QEMU and QEMU image) to John Chen (Al Nikolov)
** Windows SDK responsible John Chen
* 20100922 AP DONE: Clarify distributions priority: Ubuntu/Fedora? (Fathi/Veli/Bob/Kerry)
* AP: Draft a wiki page about distribution priorities (Jaya)

==== OBS Integration & Weekly builds * Fathi * ====

* 20100825 AP: Packaging for ISVs. Could leverage public OBS and spectacle (Intel to provide proposal / ideas).
* 20100818 AP 20100831 DONE: Modify the OBS layout (Fathi)
* 20100901 AP DONE: 64bits distributions missing (BMC#5862) (KevinWang)
** [[SDK/Release]]
* 20100820 AP DONE: packages in OBS
** [[SDK/Testing]]
** see also [[SDK/Release]]
* AP: separate maintainer and subsystem maintainer role (Fathi)
** Waiting for agreement on team proposal
* 20100915 AP: Add missing IA32 toolchain (Kevin/)
* 20100915 AP: Add missing final ARM toolchain (Fathi, Al)
* 20100820 AP: Kevinwang needs commit rights to ks file gitorious (KevinWang)
** merge request to do

==== Content ====

* MOVE THIS: 20100908 AP: Bob to sync with Veli on Qt Mobility API / impl.
* 20100908 AP: Bob to sync on WRT with Gavin Hindman (Intel). Nokia can provide names for what's missing.
** Intel and Nokia working together on this

=== Toolchains * Jarmo * 6:05 - 6:15 ===

* Generic
** Windows host toolchains
*** Toolchain is building
*** DONE: Document the process and send info to Al Nikolov (Max)

* ARM target
** 20100908 AP DONE: Come up with plan for ARM target. (Al, Fathi)
** 20100929 AP: base ARM toolchain on Kevin's work (Al)
** 20100915 AP: Create a lightweight sysroot for toolchain building (Al)

* Intel x86 target
** 20100908 AP 20100924: Push toolchain packages to dev:tool:sdk:host project (Kevin)

=== QA * Jaya * 6:15 - 6:25 ===

* First test results available
** Please comment

* 20100929 AP: Final test set for MeeGo 1.1 (Jaya)

* 20100820 AP 20100924: How to handle bugfixes of releases (Fathi)
** Create a document about MeeGo SDK related bugs (Fathi)

SDK/Tablet/VirtualBox

2011-04-01T05:49:34Z

Asinnela: /* Deploy Qt Apps to VirtualBox */ Wiki link fix

== Download and install VirtualBox ==
Download VirtualBox from the official website: [http://www.virtualbox.org/wiki/Downloads Download VirtualBox]. Before downloading and installing, you have to agree to the terms and conditions of the respective license. Please follow the installation instructions to install VirtualBox step by step.

== Create MeeGo image for VirtualBox ==
Please download the latest tablet image from this link: [http://download.meego.com/snapshots/latest/images/meego-tablet-ia32-qemu/ MeeGo Tablet Images for SDK]

=== Unpack the image tarball ===
$ tar jxf meego-tablet-ia32-qemu-${version}-raw.tar.bz2

=== Convert the image for VirtualBox ===
Converts a raw disk image to a VirtualBox Disk Image (VDI) file by VBoxManage tool(which is placed at the VirtualBox installation directory):
$ cd meego-tablet-ia32-qemu-${version}-raw
$ VBoxManage convertfromraw meego-tablet-ia32-qemu-${version}-sda.raw meego-tablet-ia32-qemu-${version}-sda.vdi

=== Run MeeGo image in VitualBox ===
Create a new virtual machine, and the setting as the screenshot below. You should choose the storage disk as the vdi image you have created in above step. For getting the advantage of CPU virtualization technologies, you should enable the VT option in VirtualBox
[[File:MeeGo Tablet VBox.png|800px]]

Then, click the start button to boot up MeeGo in VirtualBox. The image will be started as below screenshot.
[[File:Meego tablet vbox2.PNG|800px]]

== Deploy Qt Apps to VirtualBox ==
VirtualBox simulate a network card and allocate a IP address to the MeeGo platform. You can deploy Qt Apps in Qt Creator to VirtualBox as a real device. Please follow this link to enable deploy Qt Apps: [[SDK/Setup/Debugging_MeeGo_Applications#Create_a_MeeGo_Device_Configuration|Configure Qt Creator for MeeGo device]]

== Known Issues & Drawback ==
* It doesn't include a skin for VirtualBox now, you can press Wins Logo key to get the tablet back homescreen.
* The resolution in VirtualBox cannot set to 1280x800 for tablet image, the resolution is 800x600 now.

SDK/Docs/1.2/MeeGo SDK 1.2 Preview for Linux

2011-03-31T12:13:29Z

Asinnela: Wiki link fix

== Download the MeeGo SDK ==
<ol>
<li>'''Download and install the SDK'''
<table border='1' cellpadding='3px' style="padding: 0em">
<tr><th>File</th><th>File Size</th><th>MD5SUM</th><th>Installed Size</th></tr>
<tr><td>[http://download3.meego.com/MeeGoSDK/Linux/installer/meego-sdk-installer-online MeeGo SDK 1.2 Preview]</td>
<td>24.6 MB</td>
<td>d7b52900f7ffae0125da5c45ebe07d6d</td>
<td>5.2 GB</td>
</tr>
</table>
The installer does the following:
* Installs the Qt SDK tools, including Qt Creator and Qt Simulator (if selected)
* Installs QEMU virtual machine
* Installs the MeeGo Tablet target (toolchain, build libraries, and QEMU image). The SDK uses a toolchain to build applications on your host that will run on MeeGo. Inside Qt Creator the toolchain is referred to as a "Target". 
</li>
<li>'''Launch Qt Creator''' 
''Applications > Programming > Qt Creator'' 
</li>
<li>'''Next Step: [[SDK/Setup/Building_MeeGo_Applications|Building MeeGo Applications]]'''</li>
</ol>