MeeGo wiki - User contributions [en]

Build Infrastructure/Packagers Developers/CLI Part 2

2011-07-13T15:36:09Z

Vilvo: /* Summary and next steps */

= How to use the MeeGo / OBS Command Line Tools, Part 2 =

You've used the set up the 'osc' tool in [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|Part 1]] and now it's time to check out your project for local editing and build.

== Find the project to checkout ==

You can list projects you can check out using 'osc ls'. You will see your home project you created in the Web UI listed too:

$ osc ls
Trunk
Trunk:Testing
devel:base
...
home:<login>
...

== Change to your OBS area ==

Create a directory for doing work and change directory into it:

$ mkdir ~/obs
$ cd ~/obs

== Check out the desired project ==

This is a lot like using Subversion or CVS as the model is 'checkout' and 'checkin' (abbreviated 'co' and 'ci', respectively):

$ osc co home:<login>
A home:<login>
A home:<login>:bash
A home:<login>:bash/Makefile
...

You will now find your checked out project ready for modification and rebuild under home:<login>/<packagename>

== Branching a package to your home project ==

If using MeeGo OBS:

$ osc branch Trunk:Testing <packagename>

Tips, use 'bco' subcommand alias will make osc checkout the branched package meanwhile:

$ osc bco Trunk:Testing <packagename>

== Summary and next steps ==

This guide gave an introduction on how to use the osc tool to checkout sources.
The next page will cover building your project. Click [[Build_Infrastructure/Packagers_Developers/CLI_Part_3|here]] to open the 3rd part.

[[Category:Build Infrastructure]]

ARM/N900/QA

2011-03-29T10:39:15Z

Vilvo: /* Test asset */

= QA TODOs (in priority order) =

== 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.
** looking into rich-core use in MeeGo - ONGOING (sampos, rikhalon)
** set up back-end server for core processing - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

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

Brief git guide

2011-03-29T07:52:13Z

Vilvo: /* Concepts */

= Brief Git Guide =

Git is handy version control for collaborative development and testing.
This guides you briefly through basics to get started.
Only terminal usage under Linux is covered, for graphical user interfaces please refer guides available at web.

'''Note''' - this was not placed under developer nor testing because it's common for all MeeGo contributors.

== Concepts ==

Please open [http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf excellent git cheat sheet]
Work flow is illustrated in the upper-right corner of cheat sheet.
The most basic flow with existing repository goes like:

=== 1. Create ===

git clone <repository>

Example:

git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

=== 2. Change ===

<edit or create files with your favorite tools / editors>

=== 3. Commit changes ===

git add <newfile> (if you created new file)
git commit -a

Your default editor is opened and you need to write description of changes.

=== 4. Push changes to share ===

git push (this assumes you have commit rights to repository, please check with repository admin)

''' That's it! Congratulations! '''

== Pre-steps ==

=== Mandatory - Make sure you have git installed ===

Ubuntu:
sudo apt-get install git

=== Optional - If working behind ssh-proxy ===

If you are working with corporation you might need to resolve ssh-proxy challenge.

Make sure you have following $USER/.ssh/config for your user account

host proxy
HostName '''<yoursshproxyhere>'''
user '''<youruseraccounthere>'''
Compression no
LocalForward 2227 gitorious.org:22
host gitorious.org
User git
HostName 127.0.0.1
Port 2227

Run the following command:
ssh -f -N proxy
<type password for your account, if required>

''Please note that you need to open proxy connection every time you change network or disconnect/connect from network''

Now you can clone and push over ssh proxy to '''gitorious.org''', test as follows:
git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

Brief git guide

2011-03-29T07:51:53Z

Vilvo: /* Concepts */

= Brief Git Guide =

Git is handy version control for collaborative development and testing.
This guides you briefly through basics to get started.
Only terminal usage under Linux is covered, for graphical user interfaces please refer guides available at web.

'''Note''' - this was not placed under developer nor testing because it's common for all MeeGo contributors.

== Concepts ==

Please open [http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf excellent git cheat sheet]
Workflow with is illustrated in the upper-right corner of cheat sheet.
The most basic flow with existing repository goes like:

=== 1. Create ===

git clone <repository>

Example:

git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

=== 2. Change ===

<edit or create files with your favorite tools / editors>

=== 3. Commit changes ===

git add <newfile> (if you created new file)
git commit -a

Your default editor is opened and you need to write description of changes.

=== 4. Push changes to share ===

git push (this assumes you have commit rights to repository, please check with repository admin)

''' That's it! Congratulations! '''

== Pre-steps ==

=== Mandatory - Make sure you have git installed ===

Ubuntu:
sudo apt-get install git

=== Optional - If working behind ssh-proxy ===

If you are working with corporation you might need to resolve ssh-proxy challenge.

Make sure you have following $USER/.ssh/config for your user account

host proxy
HostName '''<yoursshproxyhere>'''
user '''<youruseraccounthere>'''
Compression no
LocalForward 2227 gitorious.org:22
host gitorious.org
User git
HostName 127.0.0.1
Port 2227

Run the following command:
ssh -f -N proxy
<type password for your account, if required>

''Please note that you need to open proxy connection every time you change network or disconnect/connect from network''

Now you can clone and push over ssh proxy to '''gitorious.org''', test as follows:
git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

Brief git guide

2011-03-29T07:47:22Z

Vilvo: /* Brief Git Guide */

= Brief Git Guide =

Git is handy version control for collaborative development and testing.
This guides you briefly through basics to get started.
Only terminal usage under Linux is covered, for graphical user interfaces please refer guides available at web.

'''Note''' - this was not placed under developer nor testing because it's common for all MeeGo contributors.

== Concepts ==

Please open [- http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf excellent git cheat sheet]
Workflow with is illustrated in the upper-right corner of cheat sheet.
The most basic flow with existing repository goes like:

=== 1. Create ===

git clone <repository>

Example:

git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

=== 2. Change ===

<edit or create files with your favorite tools / editors>

=== 3. Commit changes ===

git add <newfile> (if you created new file)
git commit -a

Your default editor is opened and you need to write description of changes.

=== 4. Push changes to share ===

git push (this assumes you have commit rights to repository, please check with repository admin)

''' That's it! Congratulations! '''

== Pre-steps ==

=== Mandatory - Make sure you have git installed ===

Ubuntu:
sudo apt-get install git

=== Optional - If working behind ssh-proxy ===

If you are working with corporation you might need to resolve ssh-proxy challenge.

Make sure you have following $USER/.ssh/config for your user account

host proxy
HostName '''<yoursshproxyhere>'''
user '''<youruseraccounthere>'''
Compression no
LocalForward 2227 gitorious.org:22
host gitorious.org
User git
HostName 127.0.0.1
Port 2227

Run the following command:
ssh -f -N proxy
<type password for your account, if required>

''Please note that you need to open proxy connection every time you change network or disconnect/connect from network''

Now you can clone and push over ssh proxy to '''gitorious.org''', test as follows:
git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

Brief git guide

2011-03-29T07:40:08Z

Vilvo: /* Optional - If working behind ssh-proxy */

= Brief Git Guide =

Git is handy version control for collaborative development and testing.
This guides you briefly through basics to get started.
Only terminal usage under Linux is covered, for graphical user interfaces please refer guides available at web.

== Concepts ==

Please open [- http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf excellent git cheat sheet]
Workflow with is illustrated in the upper-right corner of cheat sheet.
The most basic flow with existing repository goes like:

=== 1. Create ===

git clone <repository>

Example:

git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

=== 2. Change ===

<edit or create files with your favorite tools / editors>

=== 3. Commit changes ===

git add <newfile> (if you created new file)
git commit -a

Your default editor is opened and you need to write description of changes.

=== 4. Push changes to share ===

git push (this assumes you have commit rights to repository, please check with repository admin)

''' That's it! Congratulations! '''

== Pre-steps ==

=== Mandatory - Make sure you have git installed ===

Ubuntu:
sudo apt-get install git

=== Optional - If working behind ssh-proxy ===

Make sure you have following $USER/.ssh/config for your user account

host proxy
HostName '''<yoursshproxyhere>'''
user '''<youruseraccounthere>'''
Compression no
LocalForward 2227 gitorious.org:22
host gitorious.org
User git
HostName 127.0.0.1
Port 2227

Run the following command:
ssh -f -N proxy
<type password for your account, if required>

''Please note that you need to open proxy connection every time you change network or disconnect/connect from network''

Now you can clone and push over ssh proxy to '''gitorious.org''', test as follows:
git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

Brief git guide

2011-03-29T07:39:41Z

Vilvo: Created page with "= Brief Git Guide = Git is handy version control for collaborative development and testing. This guides you briefly through basics to get started. Only terminal usage under Lin…"

= Brief Git Guide =

Git is handy version control for collaborative development and testing.
This guides you briefly through basics to get started.
Only terminal usage under Linux is covered, for graphical user interfaces please refer guides available at web.

== Concepts ==

Please open [- http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf excellent git cheat sheet]
Workflow with is illustrated in the upper-right corner of cheat sheet.
The most basic flow with existing repository goes like:

=== 1. Create ===

git clone <repository>

Example:

git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

=== 2. Change ===

<edit or create files with your favorite tools / editors>

=== 3. Commit changes ===

git add <newfile> (if you created new file)
git commit -a

Your default editor is opened and you need to write description of changes.

=== 4. Push changes to share ===

git push (this assumes you have commit rights to repository, please check with repository admin)

''' That's it! Congratulations! '''

== Pre-steps ==

=== Mandatory - Make sure you have git installed ===

Ubuntu:
sudo apt-get install git

=== Optional - If working behind ssh-proxy ===

Make sure you have following $USER/.ssh/config for your user account

host proxy
HostName '''<yoursshproxyhere>'''
user '''<youruseraccounthere>'''
Compression no
LocalForward 2227 gitorious.org:22

host gitorious.org
User git
HostName 127.0.0.1
Port 2227

Run the following command:
ssh -f -N proxy
<type password for your account, if required>

''Please note that you need to open proxy connection every time you change network or disconnect/connect from network''

Now you can clone and push over ssh proxy to '''gitorious.org''', test as follows:
git clone git://gitorious.org/meego-quality-assurance/handset-ux-tests.git

ARM/N900/QA

2011-03-25T07:46:10Z

Vilvo: /* Test automation images */

= QA TODOs (in priority order) =

== 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 ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)
* WLAN cases
* Audio policy framework cases (lower priority)
* Camera cases (lower priority)
* Sensor data cases (Qt Mobility, lower priority)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.
** looking into rich-core use in MeeGo (sampos)
** set up back-end server for core processing - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

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

ARM/N900/QA

2011-03-25T07:43:13Z

Vilvo: /* OTS setup */

= QA TODOs (in priority order) =

== 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 (maybe later with BOSS)
** DONE - PC with F13 set up for image creation (rikhalon)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)
* WLAN cases
* Audio policy framework cases (lower priority)
* Camera cases (lower priority)
* Sensor data cases (Qt Mobility, lower priority)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.
** looking into rich-core use in MeeGo (sampos)
** set up back-end server for core processing - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

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

ARM/N900/QA

2011-03-25T07:39:38Z

Vilvo: /* OTS setup */

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - Ville Ilvonen/Riku Halonen, DONE
* OTS worker(s) for core tests - Ville Ilvonen/Riku Halonen/Timo Harkonen - DONE (2 workers up)
* Reporting to QA-reports - Ville Ilvonen/Esa-Pekka Miettinen - DONE
* Minimize automatic installation time to 10mins - Timo Makimattila, DONE
* OTS worker for UX tests - NOTSTARTED
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
** DONE - PC with F13 set up for image creation (rikhalon)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)
* WLAN cases
* Audio policy framework cases (lower priority)
* Camera cases (lower priority)
* Sensor data cases (Qt Mobility, lower priority)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.
** looking into rich-core use in MeeGo (sampos)
** set up back-end server for core processing - ONGOING (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

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

Community communication

2011-03-24T18:39:11Z

Vilvo: /* MeeGo IRC Channels */

'''This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.'''

Visit [[Community communication/Status]] for updates.

==Read Before Posting - Helping Yourself==

===Search for existing answers===
'''IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.
* '''[[MeeGo FAQ]]''': Main frequently asked questions document with links to specialized FAQs.
* '''[http://forum.meego.com/search.php Forum Search]''': Use the [http://forum.meego.com/search.php forum search page] to find answers to user questions.
* '''[http://wiki.meego.com/index.php?title=Special%3ASearch&search=&fulltext=Search Wiki Search]: Find existing documentation and helpful tips.
* '''Mailing list search''': In Google type: ''my search terms site:lists.meego.com''
* '''Search Everything''' (meego.com, mailing lists, forums, wiki, etc.): In Google type: ''my search terms site:meego.com''

===Etiquette: What to know before you post===
* '''Post in the right place''': Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
* '''Adhere to our [[Community guidelines]]''': [[Mailing list guidelines]], [[Forum/Guidelines|forum guidelines]], [[Gitorious guidelines]] and [[Wiki contribution guidelines]].
* '''File bugs in the right place''': If you found a bug, just go ahead and file it in [http://bugs.meego.com/ bugs.meego.com] ([[Quality/How To Report Bugs|instructions for how to report bugs]])

==Mailing Lists and Forums==
Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our [[Forum/Guidelines|Forum guidelines]] and [[Mailing list guidelines]].

===Announcements===
Subscribe to these lists to receive announcements.

* '''[http://lists.meego.com/listinfo/meego-announce MeeGo-announce Mailing List]''': General announcements related to the MeeGo project (announcement list - general interest)
* '''[http://lists.meego.com/listinfo/meego-security MeeGo-security Mailing List]''': MeeGo Security Announcements (announcement list for security professionals and developers)

===Users===
Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

* '''[http://forum.meego.com/forumdisplay.php?f=2 General]''': MeeGo related topics not classified in a specific subforum.
* '''[http://forum.meego.com/forumdisplay.php?f=7 Handset]''': MeeGo Handset related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=9 In-Vehicle]''': MeeGo In-Vehicle Infotainment (IVI) related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=6 Netbook]''': MeeGo Netbook related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=8 Tablet]''': MeeGo Tablet related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters]''': Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
* '''[http://forum.meego.com/forumdisplay.php?f=4 Off-Topic]''': Totally unrelated but still worth discussing between ameegos.

===Application Developers===
Ask questions and discuss techniques for developing applications to run on top of MeeGo.

* '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer Support Forum]''': Offer/get help dealing with application developer tools and APIs.
* '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-sdk Mailing List]''': MeeGo application development - using the SDK / APIs and developing applications for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-python MeeGo-python Mailing List]''': Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).
* '''MeeGo-media-dev Mailing List''': Proposed: Discussions about creating media experience applications on MeeGo.

===Contributors===
People who are contributing to the MeeGo project collaborate on these lists.

* '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List]''': Community, general operations, openness, events and other general interest questions.
* '''[http://lists.meego.com/listinfo/meego-dev MeeGo-dev Mailing List]''': Development on the MeeGo distribution - '''not''' for application development or user level questions (high volume).
* '''[http://lists.meego.com/listinfo/meego-il10n MeeGo-il10n Mailing List]''': Localization list for MeeGo community.
* '''[http://lists.meego.com/listinfo/meego-packaging MeeGo-Packaging Mailing List]''': Communication about packaging and the build system.
* '''[http://lists.meego.com/listinfo/meego-pm MeeGo-pm Mailing List]''': Program management, product management and general coordination for people working in key roles in the project.
* '''[http://lists.meego.com/listinfo/meego-touch-dev MeeGo-touch-dev Mailing List]''': MeeGo Touch Framework Development.
* '''[http://lists.meego.com/listinfo/meego-releases MeeGo-releases Mailing List]''': Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
* '''[http://lists.meego.com/listinfo/meego-qa MeeGo-qa Mailing List]''': Collaboration list on daily activities for the Quality Assurance team.
* '''[http://lists.meego.com/listinfo/meego-commits MeeGo-commits Mailing List]''': Broadcast list with auto-generated posts by people committing code into MeeGo.
* '''[http://lists.meego.com/listinfo/meego-kernel MeeGo-kernel Mailing List]''': MeeGo kernel discussions and patches.
* '''[http://lists.meego.com/listinfo/meego-architecture MeeGo-architecture Mailing List]''': MeeGo architecture discussions.
* '''[http://lists.meego.com/listinfo/meego-handset MeeGo-handset Mailing List]''': MeeGo handset program management, product management and development.
* '''MeeGo-netbook Mailing List''' (proposed): MeeGo netbook program management, product management and development.
* '''[http://lists.meego.com/listinfo/meego-ivi MeeGo-ivi Mailing List]''': MeeGo In-Vehicle Infotainment program management, product management and development.
* '''MeeGo-mirrors Mailing List''' (proposed): Communication with people who are mirroring our downloads.
* '''[http://lists.meego.com/listinfo/meego-security-discussion MeeGo-security-discussion Mailing List]''': Discussion about the MeeGo Security Framework and other security topics.
* '''[http://lists.meego.com/listinfo/meego-it MeeGo-it Mailing List]''': Discussion about IT and infrastructure for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-porting MeeGo-porting Mailing List]''': Discussions about porting MeeGo to various platforms / devices.
* '''[http://lists.meego.com/listinfo/meego-events MeeGo-events Mailing List]''': Discussions about MeeGo Conferences and other MeeGo events.
* '''[http://lists.meego.com/listinfo/meego-distribution-tools MeeGo-distribution-tools Mailing List]''': Discussion list for the [http://meego.gitorious.org/meego-developer-tools distribution development] and [http://meego.gitorious.org/meego-infrastructure-tools distribution infrastructure] tools used in MeeGo release and packaging.
* '''[http://lists.meego.com/listinfo/meego-adaptation-intel-automotive MeeGo-adaptation-intel-automotive Mailing List]''': MeeGo Intel Automotive Adaptation kernel discussion and patches.
* '''[http://lists.meego.com/listinfo/meego-tv MeeGo-tv Mailing List]''': Discussions about Connected TV, Set-Top Boxes (STB) and Media Center devices.
* '''MeeGo-Media''' (proposed): Discussions about multimedia and media-specific middleware, codecs, reference media applications, sharing frameworks and other media topics.
* '''[http://lists.meego.com/listinfo/meego-inputmethods MeeGo-Inputmethods]''': Communication channel for the [[Meego Input Methods]] project used by core developers, contributors and external input method plug-in developers.

Note: Lists without links may still be tentative and have not been created or configured yet.

==IRC==

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at [http://freenode.net/ irc.freenode.net].

===MeeGo IRC Channels===

* '''#meego''': 24/7 open discussion.
* '''#meego-meeting''': scheduled IRC meetings ([[MeeGo-Meeting IRC Schedule]]).
* '''#meego-meeting-questions''': used for questions during moderated IRC meetings (rarely used).
* '''#meego-arm''': MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
* '''#meego-dev''': MeeGo project collaboration for developers contributing to MeeGo.
* '''#meego-sdk''': Discussion about the MeeGo SDK.
* '''#meego-handset''': Collaboration for the MeeGo Handset team.
* '''#meego-art''': Graphics and theming.
* '''#meego-qa''': MeeGo QA channel
* '''#meego-python''': The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
* '''#meego-l10n''': Used for questions and discussion on localizing MeeGo
* '''#meego-bar''': Used for drinking Guinness and general off topic chat with colleagues and friends around the world
* '''#meego-fi''': Regional channel for MeeGo Network Finland. Includes discussions about MeeGo Summit FI
* '''#meego-rus''': Regional channel for MeeGo Network Russia.

===IRC How-to===

* '''MeeGo [[IRC guidelines]]'''
* '''[http://irchelp.org/irchelp/ircprimer.html IRC Primer]''': Read this if you are new to IRC.
* '''[http://freenode.net/channel_guidelines.shtml Freenode Guidelines]'''.
* '''[http://webchat.freenode.net/ IRC Webchat]''': If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
* '''[http://en.wikipedia.org/wiki/Internet_Relay_Chat_client#Clients IRC Clients]'''.

==Bugs==

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

* '''[[Quality/How To Report Bugs|How to Report Bugs]]''': Instructions, process and guidelines
* '''[http://bugs.meego.com/ bugs.meego.com]''': MeeGo Bugzilla

==Documentation==

Some of our documentation can be found on [http://meego.com MeeGo.com], but most of the documentation can be found in the [[Main Page|MeeGo Wiki]] where you can contribute by:
* Adding new documentation to help other people in the MeeGo community
* Correcting technical errors or adding additional information in the documentation
* Cleaning up the language and correcting typos

==Contributing to MeeGo==

There are also many ways that you can contribute to MeeGo beyond just discussions. See our [http://meego.com/about/contribution-guidelines Contribution Guidelines] page for more details.

Quality/QA-tools

2011-03-24T07:39:21Z

Vilvo: /* Quality assurance (QA) tools */

= 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 is also a [http://www.youtube.com/watch?v=WdXBqGdLz8I concept video] available on the tool offering for manual testing on our [http://www.youtube.com/user/meegoqatools YouTube channel].

[[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]]

Quality/QA-tools

2011-03-24T07:39:03Z

Vilvo: /* Quality assurance (QA) tools */

= Quality assurance (QA) tools =

''' We moved our discussion to #meego-qa IRC channel. 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 is also a [http://www.youtube.com/watch?v=WdXBqGdLz8I concept video] available on the tool offering for manual testing on our [http://www.youtube.com/user/meegoqatools YouTube channel].

[[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]]

Quality/QA-tools

2011-03-24T07:38:11Z

Vilvo: /* Collaboration spaces */

= Quality assurance (QA) tools =

[[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 is also a [http://www.youtube.com/watch?v=WdXBqGdLz8I concept video] available on the tool offering for manual testing on our [http://www.youtube.com/user/meegoqatools YouTube channel].

[[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/QA

2011-03-18T08:21:28Z

Vilvo: /* OTS setup */

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - Ville Ilvonen/Riku Halonen, DONE
* OTS worker(s) for core tests - Ville Ilvonen/Riku Halonen/Timo Harkonen - ONGOING (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time to 10mins - Timo Makimattila, ONGOING

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

== Error Management ==
* Error Manager Iekku Huttunen

[[Category:N900]]

ARM/N900/QA

2011-03-18T08:21:05Z

Vilvo: /* OTS setup */

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - Ville Ilvonen/Riku Halonen, DONE
* OTS worker(s) for core tests - Ville Ilvonen/Riku Halonen/Timo Harkonen - ONGOING (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time to 10mins, Timo Makimattila, ONGOING

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

== Error Management ==
* Error Manager Iekku Huttunen

[[Category:N900]]

ARM/N900/QA

2011-03-18T08:19:48Z

Vilvo: /* OTS setup */

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - Ville Ilvonen/Riku Halonen, DONE
* OTS worker(s) for core tests - Ville Ilvonen/Riku Halonen/Timo Harkonen - ONGOING (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time, Timo Makimattila, ONGOING

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Crashdb support for ARM core dumps ==

* Core dump processing and backtraces from crashing ARM processes.

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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.

== Error Management ==
* Error Manager Iekku Huttunen

[[Category:N900]]

ARM/N900/QA

2011-03-17T08:17:02Z

Vilvo:

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - DONE
* OTS worker(s) for core tests - DONE (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

= Test Execution Schedule =
* Core

* Handset UX weekly testing schedule
{| 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
|}

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

ARM/N900/QA

2011-03-17T08:16:39Z

Vilvo:

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - DONE
* OTS worker(s) for core tests - DONE (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

= Test Execution Schedule =
* Core

* Handset UX weekly testing schedule
{| 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
|}

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

== 6. QA Tasks For Developer Edition ==
There is a wiki article about the [[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.

ARM/N900/QA

2011-03-17T08:16:04Z

Vilvo: /* QA TODOs */

= QA TODOs (in priority order) =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - DONE
* OTS worker(s) for core tests - DONE (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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
|}

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

== 6. QA Tasks For Developer Edition ==
There is a wiki article about the [[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.

ARM/N900/QA

2011-03-17T08:14:54Z

Vilvo: /* Test automation images */

= QA TODOs =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - DONE
* OTS worker(s) for core tests - DONE (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

=== Test automation images ===
* Setup hourly image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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
|}

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

== 6. QA Tasks For Developer Edition ==
There is a wiki article about the [[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.

ARM/N900/QA

2011-03-17T08:14:14Z

Vilvo:

= QA TODOs =

== OTS setup and automated hourly testing ==

=== OTS setup ===
* OTS server - DONE
* OTS worker(s) for core tests - DONE (2 workers up)
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

=== Test automation images ===
* Setup image building for autotest image on own setup (maybe later with BOSS)
* We need to be able to control included test packages

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

== Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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
|}

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

== 6. QA Tasks For Developer Edition ==
There is a wiki article about the [[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.

ARM/N900/QA

2011-03-17T08:10:15Z

Vilvo:

= QA TODOs =

== 1. OTS setup ==
* OTS server
* OTS worker(s) for core tests
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

== 2. Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== 3. Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== 4. Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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
|}

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

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

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

== 6. QA Tasks For Developer Edition ==
There is a wiki article about the [[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.

ARM/N900/QA

2011-03-17T08:09:44Z

Vilvo:

= QA TODOs =

== 1. OTS setup ==
* OTS server
* OTS worker(s) for core tests
* OTS worker for UX tests
* Power consumption measurements
* Reporting to QA-reports
* Minimize automatic installation time

== 2. Applications for testing ==
* Package QML demo/example applications from http://doc.qt.nokia.com/latest/qdeclarativeexamples.html

== 3. Test asset ==
* Define what the asset includes
* Automating as many core/ux tests as possible
* Call/SMS cases will require parallel test execution support (If we want to automate those kind of tests)

== 4. Test Execution Schedule ==
* Core

* Handset UX weekly testing schedule
{| 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
|}

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

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

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

== Crashdb support for ARM core dumps ==

Core dump processing and backtraces from crashing ARM processes.

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

Quality/QA-tools/QAReports/Basic Workflow

2011-01-05T13:43:19Z

Vilvo: /* Uploading the Result File */

= Basic Workflow =

== Planning and Executing Test Runs ==

== Importing Test Results ==
In order to import new test results, you will need a user account on the MeeGo QA Reports service.

=== Filling in Test Details ===
You can input the test execution date in YYYY-MM-DD format, or click the calendar icon to choose the date from a calendar view.

Test type and hardware can be freely typed in, or you can click on the commonly used options on the right.

=== Uploading the Result File ===
If you are using a modern version of Google Chrome or Mozilla Firefox, you can drag and drop one or multiple files on the upload box. You can also click the button titled "Browse" to browse and select files from your local folders.

The QA Reports tool expects the uploaded files to be XML with the structure specified [http://meego.gitorious.org/meego-quality-assurance/test-definition/blobs/master/src/data/testdefinition-results.xsd here]. There is also legacy support for CSV files with a specific format (see [[Quality/QA-tools/QAReports/CSVFormat|QA Reports CSV Format]]).

If you upload more than one test result file, they merged into a single test report.

== Deleting a Test Report ==
If you are logged in, you can delete a test report by viewing it and clicking the Delete button next to the test report title. Deleting a report is irreversible. The report and all changes made to it are permanently removed.

== Editing Test Results ==
Majority of the data comes from the uploaded test result file, and cannot be modified afterwards, but you can make limited adjustments to some of the data and add explanatory text sections.

In order to make any of the following changes, you need to be in edit mode. To enter the editing mode, you must be logged in and viewing a report. You can then click the button labeled "Edit" next to the test report title.

=== Editing the Report Title ===
In edit mode, you can click the test report title in order to modify it. After making your changes, click the Save-button to commit them or Cancel to restore the original title.

=== Changing the Test Execution Date ===
If the report has an incorrect test execution date, listed in the summary box next to the table of contents, you can click it to make it editable. As in the upload form, you can either type a date by hand (in YYYY-MM-DD format) or click the calendar icon to use a visual date picker.

After correcting the date, press Save to commit your change or Cancel to undo.

=== Editing the Text Sections ===
All the text sections such as Test Objective, Test Environment and Quality Summary can be edited by clicking them. The content uses a slightly modified sub-set of the MediaWiki format for formatting text.

Headers and sub-headers can be added by using lines beginning with == and ===. E.g.
<pre>== Some Header ==
=== Some Sub-header ===</pre>

You can italicize a section of text by enclosing it in a pair of single quotes or bold it by using three single quotes. Example:

<pre>''This is italic''
'''This is bold'''</pre>

You can create bulleted lists by starting your lines with an asterisk. Example:

<pre>* Item 1
* Item 2
* Item 3</pre>

You can link to external pages by using the syntax <code><nowiki>[[url Title]]</nowiki></code>, for example:

<pre>[[http://meego.com MeeGo]]</pre>

As a shorthand, you can directly link to the MeeGo bug tracker by entering the bug id, e.g.

<pre>[[11780]]</pre>

The title and current status of the bug will be automatically fetched and updated to the test report.

=== Changing Individul Test Results ===
You can change the test result (pass/fail/na) of an individual test case by clicking on the result and selecting a new one from the drop down. Any change you make is committed immediately to the server.

=== Editing Test Case Notes ===
You can edit the notes of an individual test case by clicking the note field of that test case (i.e. the rightmost column in the table). The note field supports the same formatting options as all the regular text fields, with one difference: bugzilla links do not render the full bug title, but only the bug id. The title can been seen by hovering the mouse cursor over the bug id.

== Emailing and Printing Test Results ==
When viewing a test report, you can click the Print-button to access a simplified layout that is optimized for priting and emailing.

Quality/QA-tools/QAReports

2010-12-30T06:04:42Z

Vilvo:

= QA Reports =

[[File:MeeGoQAReports.png|right|415px]]

[http://qa-reports.meego.com/ MeeGo QA reports] is test reporting application for anyone testing MeeGo.

== Access to MeeGo QA reports ==

Access to '''publish''' MeeGo QA reports is provided on need and request basis. If you need access please file a request at [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance MeeGo Quality Assurance > Others]

== User Documentation ==

* [[Quality/QA-tools/QAReports/Basic_Workflow|Basic workflow]]
* [[Quality/QA-tools/QAReports/API|API Documentation]]

== Available environments ==

* [http://qa-reports.meego.com/ Production environment - http://qa-reports.meego.com]
* [http://meego.qa.leonidasoy.fi/ Staging environment - http://meego.qa.leonidasoy.fi/]

== Source code ==

* [http://meego.gitorious.org/meego-quality-assurance/qa-reports Source code in Gitorious]

== Developer information ==

* [[Quality/QA-tools/QAReports/Contributing_to_qa-reports|Contributing to MeeGo QA Reports]]
* [[Quality/QA-tools/QAReports/Setting_up_the_development_environment|Setting up a development environment]]
* [[Quality/QA-tools/QAReports/Setting_up_the_production_environment|Setting up a production environment]]

Quality/QA-tools/QAReports

2010-12-30T06:04:00Z

Vilvo: /* Access to MeeGo QA reports */

= QA Reports =

[[File:MeeGoQAReports.png|right|415px]]

[http://qa-reports.meego.com/ MeeGo QA reports] is test reporting application for the MeeGo QA teams.

== Access to MeeGo QA reports ==

Access to '''publish''' MeeGo QA reports is provided on need and request basis. If you need access please file a request at [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance MeeGo Quality Assurance > Others]

== User Documentation ==

* [[Quality/QA-tools/QAReports/Basic_Workflow|Basic workflow]]
* [[Quality/QA-tools/QAReports/API|API Documentation]]

== Available environments ==

* [http://qa-reports.meego.com/ Production environment - http://qa-reports.meego.com]
* [http://meego.qa.leonidasoy.fi/ Staging environment - http://meego.qa.leonidasoy.fi/]

== Source code ==

* [http://meego.gitorious.org/meego-quality-assurance/qa-reports Source code in Gitorious]

== Developer information ==

* [[Quality/QA-tools/QAReports/Contributing_to_qa-reports|Contributing to MeeGo QA Reports]]
* [[Quality/QA-tools/QAReports/Setting_up_the_development_environment|Setting up a development environment]]
* [[Quality/QA-tools/QAReports/Setting_up_the_production_environment|Setting up a production environment]]

Quality/QA-tools/Test packaging

2010-12-29T13:28:05Z

Vilvo: /* Test plan definition */

== 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 [http://wiki.meego.com/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.

Quality/QA-tools/QAReports

2010-12-28T08:07:49Z

Vilvo: /* QA Reports */

= QA Reports =

[[File:MeeGoQAReports.png|right|415px]]

[http://qa-reports.meego.com/ MeeGo QA reports] is test reporting application for the MeeGo QA teams.

== Access to MeeGo QA reports ==

Access to MeeGo QA reports is provided on need and request basis. If you need access please file a request at [[http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance MeeGo Quality Assurance > Others]]

== User Documentation ==

* [[Quality/QA-tools/QAReports/Basic_Workflow|Basic workflow]]
* [[Quality/QA-tools/QAReports/API|API Documentation]]

== Available environments ==

* [http://qa-reports.meego.com/ Production environment - http://qa-reports.meego.com]
* [http://meego.qa.leonidasoy.fi/ Staging environment - http://meego.qa.leonidasoy.fi/]

== Source code ==

* [http://meego.gitorious.org/meego-quality-assurance/qa-reports Source code in Gitorious]

File:MeeGoQAReports.png

2010-12-28T08:07:18Z

Vilvo: uploaded a new version of "File:MeeGoQAReports.png"

MeeGoQAReports Illustrated

File:MeeGoQAReports.png

2010-12-28T07:25:26Z

Vilvo: MeeGoQAReports Illustrated

MeeGoQAReports Illustrated

Quality/TestSuite/MCTS

2010-12-14T07:40:01Z

Vilvo:

== MeeGo Core Test Suite (MCTS)==
=== Overview ===
INTRODUCTION 
SOURCE CODE AND COMPILING 
TEST ENVIRONMENT 
EXECUTING TESTS 
TEST RESULTS 
KNOWN ISSUES 

MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 

Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design

Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light ||100% ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] || Dec. 17 for test plan

|-
| UPnP || light ||100% ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||100% ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||100% ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||100% ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||100% ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light ||100% ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || Dec. 17 for test plan

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "15" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Averate''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/QA-tools/OTS

2010-12-08T08:44:20Z

Vilvo: /* Introduction */

= OTS Index =

Welcome to the Open Test System (OTS) Wiki Index.

'''''The User Documentation applies to the 0.1 release.'''''

'''''The Developer Documentation track the 0.8 branch (currently under development - see the Project Planning section below).'''''

== Introduction ==

OTS is the '''Open Test Service''' for testing software systems on evolving hardware architectures.

It was born out of the test framework incrementally developed for use on [http://maemo.org/ Maemo] project and is in use for 24/7 testing service by [http://www.nokia.com/ Nokia].

=== What it does ===

'''OTS has the following primary functions:'''

* Distribution
* Load balancing
* Remote command running
* Hardware control
* Data Acquisition
* Data Analysis

'''OTS offers the following services:'''

* Fully Open Source
* Web server
* Extensible Architecture
* Interoperability

=== Why it does it ===

Quite simply: to increase efficiency and quality of on-device software testing.

=== How it does it ===

The [[Quality/QA-tools/OTS/Architecture | System Overview]] gives an outline of how OTS works

=== Installing ===

Follow the [[Quality/QA-tools/OTS/UserDocumentation/Installation | installation instructions]]

== Index ==

=== Architecture ===

* [[Quality/QA-tools/OTS/Architecture | Overview]]

* [[Quality/QA-tools/OTS/Components | Components]]

* [[Quality/QA-tools/OTS/Plugins | Plugins]]

* [[Quality/QA-tools/OTS/DataFlow | DataFlow]]

* [[Quality/QA-tools/OTS/Behaviour | Behaviour]]

=== APIs ===

* [[Quality/QA-tools/OTS/DeveloperDocs/OTS_Server_API | Server]]

* [http://gitorious.org/qa-tools/ots/blobs/dev_branch_0.8/ots.server/ots/server/distributor/api.py Distributor]

* [http://gitorious.org/qa-tools/ots/blobs/dev_branch_0.8/ots.results/ots/results/api.py Results]

* [http://gitorious.org/qa-tools/ots/blobs/dev_branch_0.8/ots.worker/ots/worker/api.py Worker]

=== System Wide Concerns ===

* [[Quality/QA-tools/OTS/Routing | Testrun Routing]]

* [[Quality/QA-tools/OTS/Protocols | Ports and Protocols]]

* [[Quality/QA-tools/OTS/Configuration | Configuration]]

* [[Quality/QA-tools/OTS/DeveloperDocs/OTS_Timeouts | Timeouts]]

* [[Quality/QA-tools/OTS/OptimisingThroughput | Optimising Throughput]]

* [[Quality/QA-tools/OTS/WatchingOTS | Watching OTS]]

== How to get going... ==

* [[Quality/QA-tools/OTS/UserDocumentation | User Documentation]]

* [[Quality/QA-tools/OTS/DevelopmentGuidelines | Development Guidelines]]

* [[Quality/QA-tools/OTS/DeveloperDocs | Developer Documentation]]

* [[Quality/QA-tools/OTS/DeveloperDocs/NoseTests | Setting up Nose tests]]

* [[Quality/QA-tools/OTS/CreatingAPublisher | Creating a Publisher]]

* [[Quality/QA-tools/OTS/Transition0.1-0.8 | Making the transition from 0.1 to 0.8]]

* [[Quality/QA-tools/OTS/Flashing | Flashing]]

* [[Quality/QA-tools/OTS/Contributions | Contributions]]

== Argot ==

* [[Quality/QA-tools/OTS/Glossary | Glossary]]

== Standards and Conventions ==

* [[Quality/QA-tools/OTS/Packages | Packages]]

* [[Quality/QA-tools/OTS/ErrorCodes | Error Codes]]

== Project Planning ==

* [[Quality/QA-tools/OTS/Roadmap | Roadmap]]

* [[Quality/QA-tools/OTS/DevelopmentStatus | DevelopmentStatus]]

* [[Quality/QA-tools/OTS/Meetings | Meetings]]

* [[Quality/QA-tools/OTS/ReleaseChecklist | ReleaseChecklist]]

* [[Quality/QA-tools#Release_Practices | Release Practices]]

OTS releases are done when a new release makes sense from OTS point of view. There are no scheduled releases.

== PEP ==

* [[Quality/QA-tools/OTS/PEP-MimeTypes | MimeTypes]]

* [[Quality/QA-tools/OTS/Naming | Naming]]

Web infrastructure

2010-12-07T13:31:10Z

Vilvo: /* MeeGo Services */

== 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
|Softlayer
|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
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|Softlayer
|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://news.meego.com
|Midgard
|OSU
|ready for deployment
|[http://meego.com/users/bergie Henri Bergius]
|[[News.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://downloads.meego.com
|??
|??
|active
|
|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://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|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
|active
| [http://meego.com/users/vilvo Ville Ilvonen]
|[http://wiki.meego.com/Quality/QA-tools/OTS details]
|}

Web infrastructure

2010-12-07T13:30:33Z

Vilvo: /* MeeGo Services */

== 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
|Softlayer
|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
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|Softlayer
|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://news.meego.com
|Midgard
|OSU
|ready for deployment
|[http://meego.com/users/bergie Henri Bergius]
|[[News.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://downloads.meego.com
|??
|??
|active
|
|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://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|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
|active
| Ville Ilvonen
|[http://wiki.meego.com/Quality/QA-tools/OTS details]
|}

Quality/QA-tools/Meetings

2010-12-07T13:08:14Z

Vilvo: /* QA Tools - Weekly Meetings */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held on need basis for specific topics in <code>#meego-meeting on irc.freenode.net</code>.
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-11.59.html This was agreed in the last weekly meeting held on December 7th 2010]

== Meeting Agendas and Minutes ==

=== Meeting Agenda ===

Regular meeting agenda:

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

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

2010-12-07T13:06:54Z

Vilvo: /* Regular Meeting Agenda */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

=== Meeting Agenda ===

Regular meeting agenda:

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

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

2010-12-07T11:35:42Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

=== Regular Meeting Agenda ===

Following items are covered weekly:

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

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

* Regular Meeting Agenda

'''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/MCTS/MCTS Development Guideline

2010-12-02T12:35:37Z

Vilvo: /* File Naming Structure */

= MeeGo Core Test Suite Quality Standards =

== Introduction and Importance ==
While the importance of testing needs little explaining, the relevance of maintaining quality standards may be less obvious. The standards of test documentation, packaging etc. are not as important when used for internal testing but when external users need to make use of the tests, ease of use and consistent packaging become important. MCTS will be used in hardware acceptance testing by companies not related to the test development therefore, it is important that the tests are easy to install, run and understand.

== Packaging ==
Packages must all conform to these standards and be self contained. This way, the user of the tests won't need to search for information/files.

In package names, words should be separated with a dash ('-').

For MCTS, adding a '-tests' suffix is not required as MCTS is a dedicated test suite. For test packages not contained in a dedicated test suite, the '-tests' suffix must be added.

=== Files ===
* README (See Documentation section below)
* src/ : contain source files
* utils/: contain utility and tools if any
* Makefile (or Makefile.am, configure.ac, autogen.sh, qmake)
* tests.xml (alternatively <packagename>.xml, should the tests all be thrown into the same folder, this needs to be documented in the README)
* data/: contain small data files (For big data such as media content, need separate package)
* pack.sh: the script to generate rpm package
* test.spec: spec files to create rpm package

=== File Naming Structure ===
* Use descriptive names (ie. ftp_file_send)
* Do not use numbers as test names (Numbers really don't tell the user what the test is supposed to test)
* Name length should be less than 30 characters long
* Use '_' to connect words in file names (except in package names)

=== Test Data ===
Small data files (a few KB) should be included with the tests. Larger files should be made available separately. Instructions for obtaining the data files must be placed in the README file.

Test data must be publicly available (MeeGo git, public media server etc.).

== Documentation ==

=== README File ===
A basic template for a README file can be found [[Quality/TestSuite/MCTS/readme_template|here]]. It is important to remember that the user who will be running the tests in the package may not have had previous experience with tests. Thus, the instructions should be as simple and explicit as possible.

The README file should also contain a list of tests and a description of them. If such a list would be too long, make it a separate file and mention this file in the README.

=== Description of Environment ===
While the description of the environment can be included in the README file, for complex environments, it may be worthwhile to include a separate file.
The environment description needs to be very explicit, *do not* assume that the user knows anything about your test environment.

Where possible, tests should not depend on proprietary components (hardware or software). All environmental needs should be such that they are available to anyone in the community.

The environment includes everything needed to run the test or tests. This included hardware and software configuration of the device under test as well as any equipment (and its configuration) outside the device itself.

For example:
<code>"A wireless network called 'test_net' must be accessible by the device and this network needs to be connected to the internet"</code>
This is not adequate. Several questions are left unanswered, such as: is a DHCP server expected on the network? Are specific ports required to be opened?
Descriptions of environments should be explicit and parameters (such as network name) should be modifiable in a configuration file or passed as a parameter. *Do not* make the tester dig through source code to find the requirements for the testing environment.
It is acceptable to point a user to a settings or configuration file to obtain environment information, provided that the file is commented and easy to read.

=== Further Documentation ===
With the exception of a list of tests and their description, any further information that is not critical to the running od the tests should be placed in a separate file or on the internet (with a link in the README file).

== Source Code ==

=== Header ===
Must contain:
* Copyright
* License
* Author
* Contact details (email address) for maintainer
* Changelog (optional)
A template can be found [[Mcts-header|here].

=== Coding Style ===
A common coding-style rule of thumb is provided [[Quality/TestSuite/MCTS/Code_style_common_rule|here]]. Bear in mind that consistency and readability are the primary concerns. If a library that the tests are heavily tied to breaks these common guidelines, then it is acceptable to follow the coding standard of the library. More detailed code style instructions for specific languages can be found here:
* [http://www.chris-lott.org/resources/cstyle/indhill-cstyle.html C/C++]
* [http://www.python.org/dev/peps/pep-0008/ Python]
* [http://hub.opensolaris.org/bin/view/Community+Group+on/shellstyle Shell]

==== Note on Commenting ====
The code style guide suggests commenting blocks of code rather than individual lines, but any line of code that is not self-explanatory should be commented individually (code readability is the key, so keep that in mind when deciding what, and how much, to comment).

==== Note on Relative References ====
Relative file references should always be relative to the location of the script. For example, in Python, instead of using: 
<code>
: ../../common
</code>
to refer to a directory 2 levels up from the location of the python script itself, use: 
<code>
: os.path.abspath(os.path.dirname(sys.argv[0])) + '/../../common'
</code>
While this requires the additional import of the 'os' module and is definitely a 'quick-and-dirty' solution, it will give the directory of the currently running script regardless of where it is run from (e.g. if the script is run from another directory).

== Running the Tests ==
The method used to run the tests must be described in detail in the README file. For inexperienced users, provide a sample command line: e.g. <code>To run the tests use: './mcts_package_test_name.py'</code>
Several other points should be kept in mind about the tests while they run:

=== Environment Handling ===
Tests should set up their own environment and clean the environment again at the end.
* Test must set up its own environment, any requested parameters should be set by the test itself.
* Test runs in desired environment
* Test cleans up and restores environment to original state or to a default state.

NOTE: The environment includes everything needed to run the test or tests. This included hardware and software configuration of the device under test as well as any equipment (and its configuration) outside the device itself.

=== Test Granularity ===
* Tests must be able to run in *any order* i.e. no test should depend on another test.
* Running one test must not prevent another test from running afterwards (i.e. do not damage the environment to the point that no other tests can run)
* Tests must be able to run individually. i.e. be able to run individual tests, not just whole packages.
* Thus test cases can be executed at any order, test cases can be skipped and one or certain test cases can be repeated multiple times.

=== Log and Result Files ===
Tests cases should always generate log and data files. This allows for easier analysis of results and problems, especially if the running of test cases is automated.
* Result files
** Must contain a Pass/Fail result or a measurement result etc.
** Must contain test names, so that the user can tell which result corresponds to which test
** If the test fails, major failure cause should be written to the result file
** Should contain passed steps: e.g.: Checked power on, turned power off, turned power on data transfer, turned power off
** Do not rely on what the API returns, check everything (see Result Verification Section for more information)
* Log files
** Log files must be detailed in the README file so that they can be found.
** Log files must contain test results.
** Reason for test failure should be evident from the log and result files, the developer should not need to run tests to find the cause of failure.
** It is suggested that log files be verbose and contain (at least) the following:
*** Functions Visited
*** Parameters passed (and their values) - (for tests that generate very long log files, there should be an option to disable this)
*** When a critical function or API call is passed, this should be noted

== Test Definition ==
* XML format can be found [http://gitorious.org/qa-tools/test-definition here].
* One test package corresponds one test case definition file
* Test definition file should be moved to "/usr/share/<testset>-tests/" during the install process.
* If the file containing all test definitions is called something other than "tests.xml", this should be mentioned in the README.
* All tests must be included in the tests.xml file.
* The tests.xml file should always be up to date.

== Makefile (or autoconf/automake) ==
* <code>make</code> : build test suite.
* <code>make install</code> : install whole test suite (binary, script, utils, helper, data) into /opt/{PACKAGE}, and tests.xml into /usr/share/<testpackagename>/tests.xml
* <code>make clean</code> : remove all object file and temporary files
* <code>make uninstall</code> : remove test binary, scripts, and tests.xml out of target installation directory.

== Test Design ==

=== The Objective of Testing ===
While the objective of testing is assist developers in creating software that functions correctly, quite often testing falls into the trap of attempting to demonstrate that the software works. This should be avoided.
* Do not attempt to find work-arounds for problems in the API under test: if '''A''' + '''B''' = '''C''' and that is not the obtained result, then the test must fail
* Tests should be written against the specification/documentation of software instead of against the implementation as it is the implementation itself that is under test.
* Always attempt to 'break' the software under test: Do not only test things that are known to be working, testing the unknown areas is as important as testing the commonly used functions.
* The final objective of testing is to provide information/evidence to developers, therefore, the more (and more detailed) information that the test can provide, the better.

=== Rules to Remember ===
Following rules shall be followed by test developer. Deviation from these rules are allowed only with very good grounds:
* Clear result: Test case should return clear Pass/Fail result
* Self explanatory: Test case should be easy to understand
* Avoid duplicated code: Use common functions or classes as much as possible
* Automate test under condition of stability
* Main function should kept simple and structure kept neat.
* For across-test common function, create separated lib file.
* No dependency on other test case.
* No dependency on UX or vertical specific apps.
* Use relative path to access dependency files inside test package such as helper, utilities and data (see notes on relative referencing above)
* Clean environment after test complete (see Test Granularity section).
* Enough comments (see comments section above).
* Use common Linux functions, avoid rewriting functionality that already exists.
* Avoid complicated code logic (if you have to use it, comment it!)
* Remove useless code.
* Use Timeouts to prevent test-case stall.

=== Automation ===
Automation is of great importance when testing is time sensetive and resources are limited. Where possible, tests should be automated as much as possible.

NOTE: A test is considered a manual when the 'manual="true"' field is set in the case definition.

=== Result Verification ===
Parameters under test should be verified before and after the test.

Example: BT power-on test.
Check that the BT device is off, if it is already on, then the test case may pass (because the device is on at the the end) but the test has not actually turned the device off. If the power is already on before the test starts, turn it off, then have the test turn it on. Do not accept an API call executing with no errors as a 'pass' result, check that the BT device is on after the test. At the end, return environment to default configuration.

=== Test case complexity ===
In order to meet the environment setup/tear-down requirements, a test case cannot be overly simple: e.g. a wifi data transfer case must enable a wifi device, detect a network, connect to it, transfer data and then close the connection. In this case, there is no need to write a specific network detection, connect to network or disconnect from network test as all of these functions are tested by the data transfer test.

Rather write fewer test-cases that are more flexible and thorough. The objective is not to have many tests but to test the relevant API to the required extent.

=== Dealing with Parameters ===
Parameters should be read from a configuration file wherever possible instead of being hard-coded. The configuration file should be commented (to explain what each parameter does) so that it is easy to edit. The location of the configuration file and the tests that it applies to should be described in the README file.

For example, a test that uses a GSM network to dial number and then hang up should have any network parameters and phone number (and perhaps the time before hanging up) described in a configuration file.

For tests where 1 or 2 parameters change frequently (and tests need to be re-run with the new parameters), it is acceptable to pass these as arguments to the test command line. It may be beneficial to have these parameters in the configuration file anyway, and simply have the values that are passed as arguments take priority (overwrite) the ones in the file while the test is running.

=== Test Coverage ===
For a detailed description of how to measure coverage, and what coverage actually means, please see [[Quality/TestSuite/MCTS/MCTS_API_analysis|here]].

Test coverage comes in 3 levels, a description of the levels follows below:
* Thorough
** Cover all APIs.
** Test case targets for usage (API combination) instead of single API.
** With Parm-pairs of equivalence partitioning and boundary condition (All-pairs optional)
* Average
** High risk APIs(e.g. new functionality relevant APIs) should be covered with thorough test rules
** Legacy or low risk APIs are covered only with basic tests
* Light
** Test most critical functionality

Quality/QA-tools/Meetings

2010-11-30T12:59:52Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Discussion on test report templates support at qa-reports.meego.com (#9922)
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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

2010-11-24T09:14:29Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Discussion on test report templates support at qa-reports.meego.com (#9922)
* Status check of bugs

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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

2010-11-23T12:50:35Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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

2010-11-23T11:59:18Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

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

* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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/Testplanner

2010-11-11T12:21:01Z

Vilvo:

= Testplanner =

[[File:Testplanner-ui-1.png|right|410px]]

Testplanner is a simple tool for creating and editing [[Quality/QA-tools/Test plan | test plan files]] which can be used in test execution. The key features include:
* Create and edit test plan files through graphical UI
* Easy reordering of test suites, test sets and test cases
* Open the test plan directly to [[Quality/QA-tools/Testrunner-ui | Testrunner UI]]

Testplanner is developed by [[Quality/QA-tools | QA tools team]]. You can contact us and contribute via the following channels:
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net]
* [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools File new bugs or improvement ideas to Bugzilla]
* [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=Testplanner&classification=MeeGo%20Platform&product=Development%20Tools Leave a comment or vote the items in our backlog]
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://gitorious.org/qa-tools/testplanner Source codes in Gitorious]

In addition, you can check our demo videos at Youtube:
* [http://www.youtube.com/watch?v=IQMPp5Nk4f4 Demo of version 0.0.4]
* [http://www.youtube.com/user/meegoqatools MeeGo QA tools Youtube channel]

== Installation ==

Testplanner can be installed on MeeGo Netbook UX, Ubuntu 10.04 (and newer) and Fedora 13.

=== MeeGo Netbook 1.1 ===

1. Download [http://wiki.meego.com/images/Devel-quality.repo repository file] and copy it to right place
sudo cp /home/$USER/Downloads/Devel-quality.repo /etc/yum.repos.d/

2. Inform zypper about new repository

sudo zypper addrepo /etc/yum.repos.d/Devel-quality.repo
sudo zypper update

3. Install Testplanner

sudo zypper install testplanner

=== Ubuntu ===

1. Add the following to your sources.list

deb <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/ /</nowiki>

2. Add the repository key

wget <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/Release.key</nowiki>
sudo apt-key add Release.key
rm Release.key

3. Update your PC's package information

sudo apt-get update

4. Install Testplanner

sudo apt-get install testplanner

=== Fedora 13 ===

1. Testplanner is also available from a Fedora 13 repository:

<nowiki>http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo</nowiki>

2. Copy the repository file to /etc/yum.repos.d/

3. Install the following package from the repository mentioned above

# yum install testplanner

== Basic Usage ==

The workflow with Testplanner, Testrunner UI and testrunner-lite is show in the following document [[http://wiki.meego.com/images/Testplanner_TestrunnerUI_TestrunnerLite.pdf]].

File:Devel-quality.repo

2010-11-11T12:15:59Z

Vilvo: devel-quality repository for the latest versions of MeeGo QA tools

devel-quality repository for the latest versions of MeeGo QA tools

Quality/QA-tools/Testplanner

2010-11-11T12:14:36Z

Vilvo: /* Installation */

= Testplanner =

[[File:Testplanner-ui-1.png|right|410px]]

Testplanner is a simple tool for creating and editing [[Quality/QA-tools/Test plan | test plan files]] which can be used in test execution. The key features include:
* Create and edit test plan files through graphical UI
* Easy reordering of test suites, test sets and test cases
* Open the test plan directly to [[Quality/QA-tools/Testrunner-ui | Testrunner UI]]

Testplanner is developed by [[Quality/QA-tools | QA tools team]]. You can contact us and contribute via the following channels:
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net]
* [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools File new bugs or improvement ideas to Bugzilla]
* [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=Testplanner&classification=MeeGo%20Platform&product=Development%20Tools Leave a comment or vote the items in our backlog]
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://gitorious.org/qa-tools/testplanner Source codes in Gitorious]

In addition, you can check our demo videos at Youtube:
* [http://www.youtube.com/watch?v=IQMPp5Nk4f4 Demo of version 0.0.4]
* [http://www.youtube.com/user/meegoqatools MeeGo QA tools Youtube channel]

== Installation ==

Testplanner can be installed on MeeGo Netbook UX, Ubuntu 10.04 (and newer) and Fedora 13.

=== MeeGo Netbook 1.1 ===

1. Add repository file /etc/yum.repos.d/devel-quality.repo with following content as sudo

[devel-quality]
name=devel-quality
failovermethod=priority
baseurl=http://download.meego.com/live/devel:/quality/weekly/
gpgcheck=1
enabled=1

2. Inform zypper about new repository (ar = add repository)

sudo zypper ar /etc/yum.repos.d/devel-quality.repo
sudo zypper update

3. Install Testplanner

sudo zypper install testplanner

=== Ubuntu ===

1. Add the following to your sources.list

deb <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/ /</nowiki>

2. Add the repository key

wget <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/Release.key</nowiki>
sudo apt-key add Release.key
rm Release.key

3. Update your PC's package information

sudo apt-get update

4. Install Testplanner

sudo apt-get install testplanner

=== Fedora 13 ===

1. Testplanner is also available from a Fedora 13 repository:

<nowiki>http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo</nowiki>

2. Copy the repository file to /etc/yum.repos.d/

3. Install the following package from the repository mentioned above

# yum install testplanner

== Basic Usage ==

The workflow with Testplanner, Testrunner UI and testrunner-lite is show in the following document [[http://wiki.meego.com/images/Testplanner_TestrunnerUI_TestrunnerLite.pdf]].

MeeGo Conference 2010/Unconference

2010-11-11T09:28:49Z

Vilvo: /* I plan to present ... */

Day 3 of the [http://conference2010.meego.com MeeGo Conference] will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities.

== What is an Unconference and Why should I attend? ==

We've been getting a lot of questions about the unconference day from people who aren't convinced that it is worth their time to attend. [[User:Dawnfoster|I (Dawn)]] have attended many unconferences and organized several of them, and I can honestly say that I usually get as much, if not more, out of them than I do from traditional conferences.

=== Brief Description ===

An unconference is an ad-hoc gathering organized by the attendees for the attendees. The concept originated out of a desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from participants. You never quite know what to expect at an unconference, since each one is shaped by the attendees. When you arrive on Wednesday morning, there will be an agenda framework (times / rooms), but the content for the sessions will be decided by the participants.

=== Why should I attend ===

'''To Present and Lead'''
* Anyone can present or lead a discussion, so you can talk about any topic of interest to you.
* If you submitted a session, and it wasn't approved for the main conference, but you still think it would be interesting, you can present it here.
* We will have plenty of smaller rooms for niche topics of interest to a few people - those rarely fit into a conference format, but work nicely in one of our smaller unconference rooms.
* It's a great opportunity to follow up on a topic presented in the first days and have a more detailed discussion.

'''To Collaborate and Network'''
* Use the time to collaborate with people on an interesting MeeGo project.
* Great opportunity to talk to experts about subjects not covered in the first two days.
* Network and meet other people interested in our work
* Learn more about what others need and get feedback on new ways to use MeeGo
* Collaborate on actual work related to MeeGo in smaller groups
* Have group discussions or meetings

'''To Learn and Innovate'''
* It is a great way to spot new talents, new movements, tendencies and upcoming technologies that weren't mature enough for the main conference.
* An unconference is basically like the conference, but with subjects chosen by the audience (by interest), which means there's a high chance of finding interesting topics.
* We have a community of interesting smart people, so we should expect plenty of interesting sessions.
* The flexible format allows for interesting out of the box ideas and ways to accommodate different formats.
* You are encouraged to use the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Law_of_Two_Feet Law of Two Feet] - if you go to a session and it isn't what you had hoped, you are encouraged to get up and move to another session.
* Come home with a fresh set of cutting-edge ideas and inspiration at the front of innovation within MeeGo.

=== More information ===
* [http://www.youtube.com/watch?v=7XlqEDIJzfw What is BarCamp? video] - short and worth your time to watch.
* [http://en.wikipedia.org/wiki/Barcamp BarCamp Wikipedia entry] with some history and other information.

== Session Ideas ==

'''IMPORTANT: Adding a session to the list below does not reserve a spot on the schedule board on Wednesday. The only way to guarantee a schedule slot is by showing up early and putting your session on the grid in person. See the [[#Schedule]] section below for more details.'''

=== Tips for Presenters ===

* Discussion formats work slightly better than standard conference presentations. Leading a group of people in a discussion is much more interactive and gives people a nice break from the past 2 days of presentations.
* Prepare in advance - if you plan to lead a session, prepare as you would for any other conference.
* Have a topic that isn't 45 minutes of material? Team up with one or more people with related topics and share the session.
* Respect people's time and do not allow your session to run longer than scheduled. Other people will be waiting to get into the room to set up for the next session.

=== I plan to present ... ===

Leave a note with the topic you plan to present along with your name and a link to more information about yourself.

* The title of an example topic description --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)
* [http://conference2010.meego.com/session/accounts-sso Introduction to the new Accounts & Single Sign On framework] --[[User:Mardy|Mardy]] 24 Sep 2010 11:52:11 (UTC)
* [http://conference2010.meego.com/session/content-fw-my-god-its-full-data Introduction to Tracker/Content FW: one of really innovating bits in Meego] --[[User:Ifrade|Frade]] 06 Oct 2010 13:21:00 (EETC)
* [[MeeGo_Conference2010/QtM_BoF_Unconference|QtMobility & MeeGo BoF/Unconference]] -- [[User:mikeleib|mikeleib]] 06 Oct 2010 04:03 UTC
* [[MeeGo_Conference_2010/Unconference/ARM|MeeGo ARM Discussion Forum]] -- [[User:stskeeps|stskeeps]] 07 Oct 2010 15:57 UTC
* [[MeeGo_Conference_2010/Unconference/Plasma|Plasma and QtComponents BoF]] -- [[User:mart|mart]] 07 Oct 2010 23:10 UTC
* [[MeeGo_Conference_2010/Unconference/TrackerHandsOn|Hands on BOF on making efficient SPARQL queries and mastering the different APIs of MeeGo's metadata service, Tracker]] -- [[User:pvanhoof|pvanhoof]], [[User:abustany|abustany]] 11 Oct 2010 10:34 UTC
* [http://conference2010.meego.com/session/working-together-world-ready-meego-developers-and-translators MeeGo Internationalization and Localization Discussion] [[User:margie|margie]]--A continuation of the discussion of the new process we are proposing to use for the next MeeGo release
* [http://wiki.meego.com/MeeGo_Conference_2010/Unconference/Hardware_adaptations_in_MeeGo Hardware adaptations in MeeGo] [[User:stskeeps|stskeeps]] -- An introduction to HW adaptations in MeeGo and the architecture and requirements process around it
* [http://lists.meego.com/pipermail/meego-qa/2010-November/000091.html Open test management proposal with tool support] [[User:vilvo|vilvo]] -- A proposal to make MeeGo core OS and UX profiles test management more open and how that can be supported with Quality Assurance tools.

=== I would like to see someone talk about ... ===

Have something that you want to see someone else talk about? Feel free to use this space to brainstorm topics.

* Tips for contributing code to MeeGo and getting it accepted --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)

* Q&A and technical discussion of core compliance package list --[[User:Joel|Joel Clark]] 09:04, 5 November 2010 (UTC)

== Schedule ==

=== Schedule Grid and Process for Scheduling Sessions ===

We will have a big grid on the wall where people can post their session ideas on the morning of the event (no sessions reserved in advance). Make sure you arrive on time if you plan to lead a session!

'''To Schedule a Session''':
* The schedule board will open up after the welcome is completed.
* Write your topic in big letters on your post it note.
* Include your contact information in smaller letters (name and cell phone or email address)
* Put your post it note on the board picking a room and time that looks good to you.
* Make sure that big meaty topics are in large rooms with niche topics in small rooms.

'''Things to keep in mind''':
* The schedule board is dynamic and may change at any time during the day.
* The schedule board on the wall is always the master.
* We may need to move sessions, so make sure you double check the board to make sure that you are going to the right room / time for the session you want to attend.
* Sessions that seem very similar may be asked to combine.
* We reserve the right to move things around to make sure that popular topics have large rooms.

=== Day Schedule and Grid Format ===

This is an example of how the grid will look and is for planning purposes only - '''please do not enter sessions or add other information to the grid'''

{| border="1"
!Time || Presidents 1 (sits 300) || Presidents 2 (sits 280) || Vavasour (sits 80) || 1872 area (sits 120) || Havelock (sits 130)||Box 1 (sits 20)||Box 2 (sits 20)|| Box 3 (sits 20)|| Box 4 (sits 20)|| Box 5 (sits 20)|| Box 6 (sits 20)|| Other
|-
!9:00 - 9:15 ||colspan=13|Atrium: Welcome - What is an unconference and how do I participate?
|-
!9:15 - 9:45 ||colspan=13|Atrium: Schedule board open - people post sessions on the grid.
|-
!9:45 - 10:00||colspan=13|Atrium: Schedule board adjustments (combine duplicates, adjust rooms, etc.)
|-
|10:00 - 10:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|11:00 - 11:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|12:00 - 12:45|| Lightning Talks || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!12:45 - 13:45||colspan=13|Lunch and Networking
|-
|13:45 - 14:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|14:45 - 15:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!15:30 - 16:00||colspan=13|We need to be out of Aviva no later than 16:00.
|-
!17:45||colspan=13|Doors open for the Ireland / Norway Football game.
|-
|}

Note: The BOF / Scheduled session room is out of scope of the unconference team and will be decided and planned by the content committee.

== Requirements ==

* Rooms set up - confirm that we do plan to use all of the rooms on the schedule board & we need to know which rooms have projectors.
* A bunch of 4x6" post it notes
* A schedule board pre-printed with times and rooms with spaces large enough to accommodate 4x6" post it notes (alternative is painter's tape & a wall)
* Sharpie pens

== Organizing Team ==

* Lead: [[User:Dawnfoster|Dawn Foster]]
* Notes / wiki organizer - put a process in place to allow people to take notes and maintain a copy (physical board is the master) of the schedule in the wiki.
* Schedule volunteers - 2 people (2 shifts - each working half the day) to help manage the schedule board, help people get things scheduled, update schedule changes in the wiki copy, etc.
* Note taking volunteers - each session needs one or more people to take notes and put them in the wiki

Quality/QA-tools/Testrunner

2010-11-10T12:33:10Z

Vilvo: /* Testrunner UI */

= Testrunner UI =

[[File:Testrunner-ui-1.png|right|400px]]

Testrunner UI is a simple graphical user interface for [[Quality/QA-tools/Testrunner-lite | testrunner-lite]]. It can be used for running automatic, semi-automatic and manual test cases. It takes a [[Quality/QA-tools/Test plan | test plan file]] as input, runs the selected test cases and produces results in format that can be published at [http://qa-reports.meego.com qa-reports.meego.com] XML format [http://gitorious.org/qa-tools/test-definition/blobs/master/src/data/testdefinition-results.xsd definition] is also available. Testrunner UI can also be used together with [[Quality/QA-tools/Testplanner | Testplanner]] which provides a graphical user interface for creating and editing the test plan files.

Testrunner UI is developed by [[Quality/QA-tools | QA tools team]]. You can contact us and contribute via the following channels:
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net]
* [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools File new bugs or improvement ideas to Bugzilla]
* [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=testrunner%20UI&classification=MeeGo%20Platform&product=Development%20Tools Leave a comment or vote the items in our backlog]
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list]
* [http://gitorious.org/qa-tools/testrunner-ui Source codes in Gitorious]

In addition, you can check our demo videos at Youtube:
* [http://www.youtube.com/user/meegoqatools MeeGo QA tools Youtube channel]

== Installation ==

Testrunner UI can be installed on Ubuntu 10.04 (and newer) and Fedora 13.

=== Ubuntu 10.04 ===

1. Add the following to your sources.list

deb <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/ /</nowiki>

2. Add the repository key

wget <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/Release.key</nowiki>
sudo apt-key add Release.key
rm Release.key

3. Update your PC's package information

sudo apt-get update

4. Install the host configuration package

sudo apt-get install testrunner-ui

=== Fedora 13 ===

1. Testrunner UI is also available from a Fedora 13 repository:

<nowiki>http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo</nowiki>

2. Install the following package from the repository mentioned above

# yum install testrunner-ui

== Basic Usage ==

The basic workflow goes as follows:

# Open a test definition.
# Select the test cases for execution. By default, all cases are selected.
# Drag and drop test suites, sets, and cases to change the execution order.
# Optionally enter results for manual cases and steps prior to test execution.
# Run selected or all tests and see execution progress live.
## When prompted, enter results and comments for manual cases and steps.
# After execution, view execution results in detail.
## See testrunner-lite output in a log view.
## See test case and step results and stdout/stderr output in a case detail view.
## Modify comments of manual and semi-automatic cases.
# Save the results.

Quality/Meetings

2010-11-09T15:40:48Z

Vilvo:

'''Tuesday November 9th 2010 14:30 UTC'''

* Opening/news from MeeGo QA (Vatula)
* Discussion about IRC usage (#meego-qa, others)
* Discussion about wiki.meego.com/Quality clean up
* Status of qa-tools (qa-reports, etc.)
* Status of Core OS (highlights and problems, new test packages, done executions, up-coming executions)
* Status of Handset (highlights and problems, new tests in gitorius, executions done, up-coming executions)
* Status of IVI (highlights and problems, new tests in gitorius, executions done, up-coming executions)
* Status of Netbook (highlights and problems, new tests in gitorius, executions done, up-coming executions)
* Status of SDK (highlights and problems, new tests in gitorius, executions done, up-coming executions)
* Status of Compliance (highlights and problems)

[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html Meeting minutes]

Quality/QA-tools/Meetings

2010-11-09T13:18:34Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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

2010-11-09T11:41:35Z

Vilvo: /* Meeting Agendas and Minutes */

= QA Tools - Weekly Meetings =

[[Quality/QA-tools|QA tools team]] meetings will be held weekly on Tuesdays 12:00 UTC in <code>#meego-meeting on irc.freenode.net</code>.

== Meeting Agendas and Minutes ==

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

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

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs
* 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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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'''

* Action points from last meeting
* Released items
* Priorities of development
* Status check of bugs

[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]