Quality/QA-tools

Revision as of 05:35, 14 September 2010

Quality Assurance (QA) Tools

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.

Release practices (SKELETON)

A skeleton to start/support conversation in 7.9. meeting, feel free to fix anything:

• Tag a version (in tools repository?)
• Promote it (to whom?)
• Verify feature/bug with nightly build
• Make a demo video
• Update bugzilla status

Proposal for Tool maintainers

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?

Team communication is in English and takes place on #meego-qa-tools IRC channel on irc.freenode.net

User Experience

If you are interested in user experience work regarding QA tools, you can find more information here.

Targets

* 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."

Enhancements and bugs

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

Meetings will be held weekly in #meego-meeting on irc.freenode.net.

Tuesday September 7th 2010 12:00 UTC - Meeting Agenda and Minutes

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

Minutes of the meeting

Tuesday August 31th 2010 12:00 UTC - Meeting agenda and minutes

 * 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

Minutes of the meeting

Team Members

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

Our collaboration spaces are:

• meego-dev@meego.com mailing list, please prefix with 'QA-tools' for team related topics.
  • Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
• #meego-qa-tools IRC channel on irc.freenode.net
• Gitorious team, http://gitorious.org/qa-tools (to be moved meego.gitorious.org)
• MeeGo OBS - devel:quality
• This wiki area
• ServiceOS
• PXEInstallation