Contents |
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.
Anyone is welcome to contribute and non-member contributions will be treated with same process and review as member contributions. We follow MeeGo contribution guidelines. In addition, you may take personal clone from our git repositories and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.
A skeleton to start/support conversation in 7.9. meeting, feel free to fix anything:
Proposal is based on developer experience with particular tool/package or seniority. Tool maintainers will be agreed in the next meeting In practice only tool maintainers will have write and review right to particular repository - later several people may have rights to repository based on merit (as proposed by tool maintainer). Other must follow MeeGo contribution guidelines to submit patches or personal clone + merge request approach.
The maintainer of the tree should update the changelog.
Question: Should there also be a "backup" maintainer, in case someone is on vacation or sick leave?
| Tool | Maintainer | IRC nick |
| test-definition | Sampo Saaristo | samposa |
| testrunner-lite | Sampo Saaristo | samposa |
| eat - enables automated testing | Timo Härkönen | timoph |
| ots - open testing system | Teemu Vainio | tvainio |
| testrunner user interface | Kyösti Ranto | kyranto |
| MeeGo Core Test Suite | Matti Salmi and Jeff Zheng | N/A and xzheng |
| MeeGo Netbook Test Suite | Jeff Zheng | xzheng |
| Model-Based Testing adapter for qtuitest | Riku Halonen | rikhalon |
| MIN test framework | Sampo Saaristo | samposa |
Team communication is in English and takes place on #meego-qa-tools IRC channel on irc.freenode.net
If you are interested in user experience work regarding QA tools, you can find more information here.
* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance * Currently test reports are published manually to wiki * Improve MeeGo test automation (execution and software installation) - target from MeeGo release engineering
"As Core OS release release manager I want to verify trunk:testing packages frequently so that I know the quality of nightly/weekly releases."
Want to report an enhancement idea or bug to us? - Please do it here
* Assigned enhancemens - Working on it * All open enhancements and bugs in priority order
Meetings will be held weekly in #meego-meeting on irc.freenode.net.
* Tool maintainers and substitutes * Release practices * Status check of bugs and development
* Short intro for project targets and tools we work with * Status of open bugs / features at bugs.meego.com * Review of released demo videos * Review of contribution guidelines
The current team members are (in no particular order):
| Name | Role | Affiliation | IRC nickname |
| Ville Ilvonen | Team lead (act.) | Nokia | vilvo |
| Riku Halonen | Team member | Nokia | rikhalon |
| Kari Sievi | Team member | Digia | sievi |
| Timo Härkönen | Team member | Digia | timoph |
| Carol Rus | Team member | Digia | carrus |
| Sami Lahtinen | Team member | Digia | slahtinen |
| Raimo Gratseff | Team member | Digia | rrraimo |
| Kyösti Ranto | Team member | Digia | kyranto |
| Arto Sinnelä | Team member | Digia | asinnela |
| Joonas Kylänpää | Team member | Digia | Kaadlajk |
| Timo Mäkimattila | Team member | Digia | timakima |
| Sampo Saaristo | Team member | Sofica | sampos |
| Ling Yu | Team member | Intel | - |
| Jing Wang | Team member | Intel | - |
| Teemu Vainio | Team member | Ixonos | tvainio |
| Tuomo Mäkinen | Team member | Ixonos | - |
| Jouni Leppäkases | Team member | Ixonos | jouni |
| Tom Galvin | Team member | Ixonos | - |
Our collaboration spaces are: