This page provides information on the development activities and practices of QA tools. The focus is on presenting things that are relevant for people interested in developing the tools. Developer-oriented content from the main page of QA tools will be moved here and the main page will become more focused on end-user needs.
Tool maintainers are selected based on developer experience with particular tool/package or seniority. Tool maintainers have been agreed in the QA-tools meeting Tuesday September 7th 2010. Changes, if needed, are discussed also there.
In practice only tool maintainers will have commit and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Others must follow MeeGo contribution guidelines to submit patches or personal clone + merge request approach.
The maintainer of the tree shall update the changelog.
|Tool (link to wiki page)||Gitorious||Maintainer||Substitute|
|test-definition||Gitorious||Sampo Saaristo||Timo Härkönen|
|testrunner-lite||Gitorious||Sampo Saaristo||Kyösti Ranto|
|Testrunner||Gitorious||Kyösti Ranto||Timo Härkönen|
|eat - enables automated testing||Gitorious||Timo Härkönen||Timo Mäkimattila|
|ots - open testing system||Gitorious||Teemu Vainio||Tom Galvin|
|MeeGo Automated installer||Gitorious||Timo Härkönen||N/A|
|MeeGo Core Test Suite||Gitorious||Matti Salmi||Jeff Zheng|
|MeeGo Netbook Test Suite||Gitorious||Jeff Zheng||N/A|
|Model-Based Testing adapter for qtuitest||Gitorious||Riku Halonen||N/A|
|MIN test framework||Gitorious||Sampo Saaristo||Timo Mäkimattila|
|Testability Driver||Gitorious||Petri Kiiskinen||Tatu Lahtela|
|Rich Core dumper||Gitorious||Carol Rus||Raimo Gratseff|
|Crash Reporter||Gitorious||Carol Rus||Raimo Gratseff|
|Crash Reporter settings||Gitorious||Carol Rus||Raimo Gratseff|
|Hardware Accessory for Testing (HAT)||Gitorious||Marko Junttila||Riku Halonen|
|QA Reports||Gitorious||Sami Hangaslammi||Jarno Keskikangas|
|Scripts and utils||Gitorious||N/A||N/A|
|MeeGo Fast Feedback Testing (MeeGo-FFT)||Gitorious||Alexey Kuznetsov||Timo Härkönen|
|Service OS based Flasher||Gitorious||Jing Wang||N/A|
|Qpid C wrapper library - libcqpid||Gitorious||Sami Lahtinen||N/A|
If you are interested in the user experience work regarding these tools, you can find more information here.
The figure below tries to summarize the relations and tasks of the tools when used in test automation context.
Here is the workflow for QA tools release practices.
|Developer||Anyone who wants to participate in qa-tools development|
|VCS Maintainer||Component owner who has commit rights in version control system (VCS)|
|Package Maintainer||Integrator whose responsibility is the OBS packaging|
|Release Management||Third party who is responsible of trunk:testing releases(?)|
Kivio file: File:Release.flw
Topic: Integration request: package-name version
PACKAGE: package-name TAG: tag name URL: link to sources CHANGES: short description of changes containing bugs.meego.com bug numbers of fixed bugs
YouTube is a good way to communicate new features. You can find existing demo videos on meegoqatools channel on Youtube.
If you shoot a video to YouTube, promote it on meego-qa mailing list!
You can find some hints how to shoot, edit, and upload a video here: YouTube_Hints
To make sure fixes are released without delay, check that the following conditions are met