MeeGo wiki - User contributions [en]

Quality/QA-tools/Meetings

2011-07-26T08:52:33Z

Jwang: /* Previous Meeting Minutes */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Aug 02th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-26-07.55.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-19-07.57.html Tuesday Jul 19st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

TimedLaunch

2011-07-26T08:41:17Z

Jwang: Created page with "=== Introduction === Precisely collect application launch time automatically. === Source Code === [https://meego.gitorious.org/meego-quality-assurance/timed-launcher git source]"

=== Introduction ===
Precisely collect application launch time automatically.

=== Source Code ===
[https://meego.gitorious.org/meego-quality-assurance/timed-launcher git source]

CleanPowerCycle

2011-07-26T08:38:18Z

Jwang: Created page with "=== Introduction === A kind of power boot stress test tool. Repeatedly reboot device with specified times and wait time. === Source Code === [http://meego.gitorious.org/meego-q..."

=== Introduction ===
A kind of power boot stress test tool. Repeatedly reboot device with specified times and wait time.

=== Source Code ===
[http://meego.gitorious.org/meego-quality-assurance/cleanpowerc git source]

Quality/QA-tools/Meetings

2011-07-26T08:32:12Z

Jwang: /* Next meeting */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Aug 02th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-26-07.55.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-19-07.57.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quality/QA-tools/Meetings

2011-07-26T08:31:57Z

Jwang: /* Next meeting */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Aug 08th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-26-07.55.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-19-07.57.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quality/QA-tools/Meetings

2011-07-26T08:31:21Z

Jwang: /* Previous Meeting Minutes */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Jul 19th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-26-07.55.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-19-07.57.html Tuesday Jul 26st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

2011-07-26T08:28:00Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

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

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

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

 
[[Category:QA]]

Memory eater

2011-07-20T08:34:25Z

Jwang: Created page with "=== Overview === A small memory tool to measure system memory footprint by eat memory Mb by Mb till swap happen. It is the most accurate method to measure system memory usage. *..."

=== Overview ===
A small memory tool to measure system memory footprint by eat memory Mb by Mb till swap happen. It is the most accurate method to measure system memory usage.
* Both free and top command can't reflect real system memory usage accurately.
* /proc/sys/vm/swapiness value can affect result.

=== Source Code ===
[https://meego.gitorious.org/meego-quality-assurance/mem-eater memEater git]

Power Diablo

2011-07-20T08:24:56Z

Jwang: Created page with "=== Overview === * powerDiablo is a tool used for exhausting all power-sensitive resources like CPU, GPU, I/O etc. It include configurable CPU, GPU workloads, and device power co..."

=== Overview ===
* powerDiablo is a tool used for exhausting all power-sensitive resources like CPU, GPU, I/O etc. It include configurable CPU, GPU workloads, and device power control. It can be brought up for one resource (like CPU) or any combination of all supported resources.
* powerDiablo can be used to validate the maximum power consumption scenario.

=== Source Code ===
[https://meego.gitorious.org/meego-quality-assurance/power-diablo powerDiablo git]

System Monitor

2011-07-20T08:20:53Z

Jwang: Created page with "=== Overview === * Run as daemon to monitor whole system status, including all process's CPU, memory and power relevant indicators. * The result can be saved as google chart base..."

=== Overview ===
* Run as daemon to monitor whole system status, including all process's CPU, memory and power relevant indicators.
* The result can be saved as google chart based html.

=== Source Code ===
[https://meego.gitorious.org/meego-quality-assurance/sys-mon sysMon git]

Quality/QA-tools

2011-07-20T08:19:21Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

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

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

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

 
[[Category:QA]]

Environment collector

2011-07-19T08:26:55Z

Jwang: Created page with "=== Overview === * Collect Linux environment info include BIOS, kernel, Gfx, File system and HW platform information. === Source Code === [http://meego.gitorious.org/meego-qual..."

=== Overview ===
* Collect Linux environment info include BIOS, kernel, Gfx, File system and HW platform information.

=== Source Code ===
[http://meego.gitorious.org/meego-quality-assurance/env-collector envCollector git]

Quality/QA-tools

2011-07-19T08:25:47Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

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

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

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

 
[[Category:QA]]

Video performance

2011-07-19T08:25:00Z

Jwang: Created page with "=== Overview === * In media performance test, one important indicator is real time frame rate. Usually, it’s difficult to get the data at media framework(such as GStreamer and ..."

=== Overview ===
* In media performance test, one important indicator is real time frame rate. Usually, it’s difficult to get the data at media framework(such as GStreamer and helix) since it depends on different demux, also it’s undefined to get the framerate at media player(such as totem) level since many media player has no such option.
* The tool is based on XDamage extension. The frame rate is got by counting the number of XDamage notification event received per second. With XDamage, X server will sent notification to client once there is Drawable modification.

=== Source Code ===
[https://meego.gitorious.org/meego-quality-assurance/video-perf videoPerf git]

Application Monitor

2011-07-19T08:22:41Z

Jwang:

=== Overview ===
Monitor system runtime indicators - CPU, memory, power status.
* A light-weight tool running background to monitor specified application or applications. It consumes extremely * low resources.
* Collect application runtime data including CPU usage, memory footprint, etc
* Collect System runtime data including Cn residency time, Wakeup times per second, etc
* Show a curve graph of each indicator
* Data summary

=== Source Code ===
[http://meego.gitorious.org/meego-quality-assurance/app-mon appMon git]

Application Monitor

2011-07-19T08:20:52Z

Jwang: /* Source Code */

=== Overview ===
Monitor system runtime indicators - CPU, memory, device driver, hw configuration, compiler etc.

=== Source Code ===
[http://meego.gitorious.org/meego-quality-assurance/env-collector envCollector git]

Application Monitor

2011-07-19T08:20:23Z

Jwang:

Application Monitor

2011-07-19T08:19:00Z

Jwang: Created page with "=== Overview === Monitor runtime indicators - CPU, memory, power for specified apps === Source Code === [http://meego.gitorious.org/meego-quality-assurance/env-collector git]"

=== Overview ===
Monitor runtime indicators - CPU, memory, power for specified apps

=== Source Code ===
[http://meego.gitorious.org/meego-quality-assurance/env-collector git]

Quality/QA-tools

2011-07-19T08:14:53Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

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

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

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

 
[[Category:QA]]

Quality/QA-tools/Meetings

2011-07-19T04:59:34Z

Jwang: /* Next meeting */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Jul 19th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quality/QA-tools/Meetings

2011-07-19T04:59:13Z

Jwang: /* Previous Meeting Minutes */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday Jun 27th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business

== Previous Meeting Minutes ==
[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-07-12-07.57.html Tuesday Jul 12st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-21-07.58.html Tuesday Jun 21st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-14-07.58.html Tuesday Jun 14th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-06-07-07.59.html Tuesday Jun 7th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-31-07.59.html Tuesday May 31st 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-17-07.58.html Tuesday May 17th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-10-07.59.html Tuesday May 10th 2011 08:00 UTC]

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Tuesday May 3rd 2011 08:00 UTC]

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

Testkit Howto

2011-06-20T13:40:47Z

Jwang: /* Source Code Git */

== How to Use Testkit ==
=== Overview ===

Testkit is one testing execution environment, which is composed by testkit-manager and testkit-lite.
Testkit-manager represents a user interface front-end in browser, with the webUI interface, it manages the auto tests execution remotely, and provides unified webUI to help the manual tests execution.
Testkit-lite is the default core test runner driving test execution in testkit-manager and it also provides more comprehensive options for your testing in command line mode.

=== Source Code Git ===
[https://meego.gitorious.org/meego-quality-assurance/testkit-lite testit-lite git]

[https://meego.gitorious.org/meego-quality-assurance/testkit-manager testkit-manager git]

=== Installation ===
1. Download testkit-lite and testkit-manager packages(rpm) from the download page, or source code from gitorious
[http://meego.gitorious.org/meego-quality-assurance/testkit-lite testit-lite git]
[https://meego.gitorious.org/meego-quality-assurance/testkit-manager testkit-manager git]

2. Install the packages.

rpm -ivh testkit-lite-<version>.<architecture>.rpm
rpm -ivh testkit-manager-<version>.<architecture>.rpm

Before that, you might need to install the following dependency packages:

perl-XML-Simple, perl-XML-SAX, perl-JSON, man, python-lxml

3. Startup the testkit-manager web server

/opt/testkit/manager/webapps/bin/testkit_start.pl [port-number]

4. Visit the testing page: http://''test-machine-name'':8890

'''Test Package Requirements:'''

Test package should follow the guideline: http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline

*The test packages for testkit should have one tests.xml which aligns with schema file testdefinition-syntax.xsd.
*The tests.xml should be settled down to /usr/share/<packagename>.
*The test materials (script, binary, data …) is always under /opt/<packagename>.

=== Using Web UI ===
1. In the browser you will find the tests packages overview in page “VIEW TEST”. Click each package

[[File:image001.jpg]]

2. To run the target tests packages, click page “SELECT TEST”. Then tick target test packages and click “Run Tests”.

[[File:image002.jpg]]

3. To save time to select the same test packages the next time, save the selection set as one profile.

[[File:image003.jpg]]

4. After “Run Tests” is clicked in page “SELECT TEST”, it jumps to page “EXECUTE TEST” and start the auto tests execution.

[[File:image004.jpg]]

5. In page “EXECUTE TEST”, you can also select the existed profile directly and click “start” to start the execution, during the execution, could “stop” the current execution.

[[File:image005.jpg]]

6. After execution ends from page “SELECT TEST”, it jumps to page “DETAIL TEST REPORT”. In this page, you can check the execution brief summary.

[[File:image006.jpg]]

7. Click “VIEW TEST LOG” to view the detail execution log.

[[File:image007.jpg]]

8. Click “VIEW HISTORY” to see all the test history entry link. This page could be also redirected by “TEST REPORT” tab.

[[File:image008.jpg]]

9. If the selected tests package include some manual tests, click “RUN MANUAL TEST” in page “DETAIL TEST REPORT” in step 6.

[[File:image009.jpg]]

Click each test from the left frame, view the detail steps and then select PASS, FAIL or N/A, “SAVE RESULT” to save this test’s result.

After all manual tests are executed, click “FINISH TEST” to end up the manual tests execution. Note that the once the “FINISH TEST” is clicked, it means one round of test cycle is finished that no chance to modify the test results any more. The “RUN MANUAL TEST” button in “DETAIL TEST REPORT” will be removed.

[[File:image010.jpg]]

=== Using Command Line UI ===
Testkit-lite is the default core test runner in testkit-manager and it provides more comprehensive options for your testing in command line mode.

==== How to execute ====
1. You can simply conduct one or more tests.xml:

testkit-lite -f <somewhere1>/tests.xml <somewhere2>/tests.xml

2. You can also arrange several tests.xml to one testsxmlconfig, and run:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig

Also, it supports multi testsxmlconfig:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig <somewhere2>/testsxmlconfig

The testsxmlconfig is like this:
/opt/browser/tests.xml
/opt/ofono/tests.xml
/opt/gfx/tests.xml
/opt/pulseaudio/tests.xml
3. If you want to validate one new tests.xml:
testkit-lite -f tests.xml -V
4. If you just want to get the statistic (such as the testcases number or the structure), dryrun could help:
testkit-lite -f tests.xml -D
5. If you want to execute auto tests:
testkit-lite -f tests.xml
6. If you just want to execute manual tests:
testkit-lite -f tests.xml -M
7. If you want to execute all the auto and manual tests:
testkit-lite -f tests.xml -A
8. If you just want to execute the significant tests:
testkit-lite -f tests.xml -S
9. If you want to choose some filters:
testkit-lite -f tests1.xml tests2.xml --level level1 level2 --type type1 type2 --Ntestcase gfx1 gfx2...
Note that the test cases will be filtered out by both black rules and white rules.

10. At last, you can freely compose the above paramters together:
testkit-lite -f tests1.xml tests2.xml --testxmlconfig config1 config2 -D -A -S -C --level level1 level2 --type type1 type2 ...
11. One more parameter is prepared for customized compatible mode for test report:
testkit-lite -f tests.xml -C
12. Notes:

testkit-lite enables only automatic tests by default. Obviously -A and -M are conflict options.

==== How to get result ====
1. testkit-lite's TestLog is stored to /opt/testkit/lite/latest after execution, you can also check the history results in /opt/testkit/lite/yyyy-mm-dd-HH:MM:SS.NNNNNN.

2. Two kinds of test report will be generated:

1)<tests xml name>.textresult, e.g.

[[File:image011.jpg|400px]]

2)<tests xml name>.xmlresult

xml result files aligned with schema files: /opt/testkit-lite/xsd/testdefinition-results.xsd, e.g.

[[File:image012.jpg|800px]]

Detail Options of testkit-lite:

[[File:image013.jpg|400px]]

Testkit Howto

2011-06-20T13:40:27Z

Jwang: /* How to Use Testkit */

== How to Use Testkit ==
=== Overview ===

Testkit is one testing execution environment, which is composed by testkit-manager and testkit-lite.
Testkit-manager represents a user interface front-end in browser, with the webUI interface, it manages the auto tests execution remotely, and provides unified webUI to help the manual tests execution.
Testkit-lite is the default core test runner driving test execution in testkit-manager and it also provides more comprehensive options for your testing in command line mode.

=== Source Code Git ===
[http://meego.gitorious.org/meego-quality-assurance/testkit-lite testit-lite git]

[https://meego.gitorious.org/meego-quality-assurance/testkit-manager testkit-manager git]

=== Installation ===
1. Download testkit-lite and testkit-manager packages(rpm) from the download page, or source code from gitorious
[http://meego.gitorious.org/meego-quality-assurance/testkit-lite testit-lite git]
[https://meego.gitorious.org/meego-quality-assurance/testkit-manager testkit-manager git]

2. Install the packages.

rpm -ivh testkit-lite-<version>.<architecture>.rpm
rpm -ivh testkit-manager-<version>.<architecture>.rpm

Before that, you might need to install the following dependency packages:

perl-XML-Simple, perl-XML-SAX, perl-JSON, man, python-lxml

3. Startup the testkit-manager web server

/opt/testkit/manager/webapps/bin/testkit_start.pl [port-number]

4. Visit the testing page: http://''test-machine-name'':8890

'''Test Package Requirements:'''

Test package should follow the guideline: http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline

*The test packages for testkit should have one tests.xml which aligns with schema file testdefinition-syntax.xsd.
*The tests.xml should be settled down to /usr/share/<packagename>.
*The test materials (script, binary, data …) is always under /opt/<packagename>.

=== Using Web UI ===
1. In the browser you will find the tests packages overview in page “VIEW TEST”. Click each package

[[File:image001.jpg]]

2. To run the target tests packages, click page “SELECT TEST”. Then tick target test packages and click “Run Tests”.

[[File:image002.jpg]]

3. To save time to select the same test packages the next time, save the selection set as one profile.

[[File:image003.jpg]]

4. After “Run Tests” is clicked in page “SELECT TEST”, it jumps to page “EXECUTE TEST” and start the auto tests execution.

[[File:image004.jpg]]

5. In page “EXECUTE TEST”, you can also select the existed profile directly and click “start” to start the execution, during the execution, could “stop” the current execution.

[[File:image005.jpg]]

6. After execution ends from page “SELECT TEST”, it jumps to page “DETAIL TEST REPORT”. In this page, you can check the execution brief summary.

[[File:image006.jpg]]

7. Click “VIEW TEST LOG” to view the detail execution log.

[[File:image007.jpg]]

8. Click “VIEW HISTORY” to see all the test history entry link. This page could be also redirected by “TEST REPORT” tab.

[[File:image008.jpg]]

9. If the selected tests package include some manual tests, click “RUN MANUAL TEST” in page “DETAIL TEST REPORT” in step 6.

[[File:image009.jpg]]

Click each test from the left frame, view the detail steps and then select PASS, FAIL or N/A, “SAVE RESULT” to save this test’s result.

After all manual tests are executed, click “FINISH TEST” to end up the manual tests execution. Note that the once the “FINISH TEST” is clicked, it means one round of test cycle is finished that no chance to modify the test results any more. The “RUN MANUAL TEST” button in “DETAIL TEST REPORT” will be removed.

[[File:image010.jpg]]

=== Using Command Line UI ===
Testkit-lite is the default core test runner in testkit-manager and it provides more comprehensive options for your testing in command line mode.

==== How to execute ====
1. You can simply conduct one or more tests.xml:

testkit-lite -f <somewhere1>/tests.xml <somewhere2>/tests.xml

2. You can also arrange several tests.xml to one testsxmlconfig, and run:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig

Also, it supports multi testsxmlconfig:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig <somewhere2>/testsxmlconfig

The testsxmlconfig is like this:
/opt/browser/tests.xml
/opt/ofono/tests.xml
/opt/gfx/tests.xml
/opt/pulseaudio/tests.xml
3. If you want to validate one new tests.xml:
testkit-lite -f tests.xml -V
4. If you just want to get the statistic (such as the testcases number or the structure), dryrun could help:
testkit-lite -f tests.xml -D
5. If you want to execute auto tests:
testkit-lite -f tests.xml
6. If you just want to execute manual tests:
testkit-lite -f tests.xml -M
7. If you want to execute all the auto and manual tests:
testkit-lite -f tests.xml -A
8. If you just want to execute the significant tests:
testkit-lite -f tests.xml -S
9. If you want to choose some filters:
testkit-lite -f tests1.xml tests2.xml --level level1 level2 --type type1 type2 --Ntestcase gfx1 gfx2...
Note that the test cases will be filtered out by both black rules and white rules.

10. At last, you can freely compose the above paramters together:
testkit-lite -f tests1.xml tests2.xml --testxmlconfig config1 config2 -D -A -S -C --level level1 level2 --type type1 type2 ...
11. One more parameter is prepared for customized compatible mode for test report:
testkit-lite -f tests.xml -C
12. Notes:

testkit-lite enables only automatic tests by default. Obviously -A and -M are conflict options.

==== How to get result ====
1. testkit-lite's TestLog is stored to /opt/testkit/lite/latest after execution, you can also check the history results in /opt/testkit/lite/yyyy-mm-dd-HH:MM:SS.NNNNNN.

2. Two kinds of test report will be generated:

1)<tests xml name>.textresult, e.g.

[[File:image011.jpg|400px]]

2)<tests xml name>.xmlresult

xml result files aligned with schema files: /opt/testkit-lite/xsd/testdefinition-results.xsd, e.g.

[[File:image012.jpg|800px]]

Detail Options of testkit-lite:

[[File:image013.jpg|400px]]

Testkit Howto

2011-06-20T13:36:24Z

Jwang: /* Installation */

== How to Use Testkit ==
=== Overview ===

Testkit is one testing execution environment, which is composed by testkit-manager and testkit-lite.
Testkit-manager represents a user interface front-end in browser, with the webUI interface, it manages the auto tests execution remotely, and provides unified webUI to help the manual tests execution.
Testkit-lite is the default core test runner driving test execution in testkit-manager and it also provides more comprehensive options for your testing in command line mode.

=== Installation ===
1. Download testkit-lite and testkit-manager packages(rpm) from the download page, or source code from gitorious
[http://meego.gitorious.org/meego-quality-assurance/testkit-lite testit-lite git]
[https://meego.gitorious.org/meego-quality-assurance/testkit-manager testkit-manager git]

2. Install the packages.

rpm -ivh testkit-lite-<version>.<architecture>.rpm
rpm -ivh testkit-manager-<version>.<architecture>.rpm

Before that, you might need to install the following dependency packages:

perl-XML-Simple, perl-XML-SAX, perl-JSON, man, python-lxml

3. Startup the testkit-manager web server

/opt/testkit/manager/webapps/bin/testkit_start.pl [port-number]

4. Visit the testing page: http://''test-machine-name'':8890

'''Test Package Requirements:'''

Test package should follow the guideline: http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline

*The test packages for testkit should have one tests.xml which aligns with schema file testdefinition-syntax.xsd.
*The tests.xml should be settled down to /usr/share/<packagename>.
*The test materials (script, binary, data …) is always under /opt/<packagename>.

=== Using Web UI ===
1. In the browser you will find the tests packages overview in page “VIEW TEST”. Click each package

[[File:image001.jpg]]

2. To run the target tests packages, click page “SELECT TEST”. Then tick target test packages and click “Run Tests”.

[[File:image002.jpg]]

3. To save time to select the same test packages the next time, save the selection set as one profile.

[[File:image003.jpg]]

4. After “Run Tests” is clicked in page “SELECT TEST”, it jumps to page “EXECUTE TEST” and start the auto tests execution.

[[File:image004.jpg]]

5. In page “EXECUTE TEST”, you can also select the existed profile directly and click “start” to start the execution, during the execution, could “stop” the current execution.

[[File:image005.jpg]]

6. After execution ends from page “SELECT TEST”, it jumps to page “DETAIL TEST REPORT”. In this page, you can check the execution brief summary.

[[File:image006.jpg]]

7. Click “VIEW TEST LOG” to view the detail execution log.

[[File:image007.jpg]]

8. Click “VIEW HISTORY” to see all the test history entry link. This page could be also redirected by “TEST REPORT” tab.

[[File:image008.jpg]]

9. If the selected tests package include some manual tests, click “RUN MANUAL TEST” in page “DETAIL TEST REPORT” in step 6.

[[File:image009.jpg]]

Click each test from the left frame, view the detail steps and then select PASS, FAIL or N/A, “SAVE RESULT” to save this test’s result.

After all manual tests are executed, click “FINISH TEST” to end up the manual tests execution. Note that the once the “FINISH TEST” is clicked, it means one round of test cycle is finished that no chance to modify the test results any more. The “RUN MANUAL TEST” button in “DETAIL TEST REPORT” will be removed.

[[File:image010.jpg]]

=== Using Command Line UI ===
Testkit-lite is the default core test runner in testkit-manager and it provides more comprehensive options for your testing in command line mode.

==== How to execute ====
1. You can simply conduct one or more tests.xml:

testkit-lite -f <somewhere1>/tests.xml <somewhere2>/tests.xml

2. You can also arrange several tests.xml to one testsxmlconfig, and run:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig

Also, it supports multi testsxmlconfig:

testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig <somewhere2>/testsxmlconfig

The testsxmlconfig is like this:
/opt/browser/tests.xml
/opt/ofono/tests.xml
/opt/gfx/tests.xml
/opt/pulseaudio/tests.xml
3. If you want to validate one new tests.xml:
testkit-lite -f tests.xml -V
4. If you just want to get the statistic (such as the testcases number or the structure), dryrun could help:
testkit-lite -f tests.xml -D
5. If you want to execute auto tests:
testkit-lite -f tests.xml
6. If you just want to execute manual tests:
testkit-lite -f tests.xml -M
7. If you want to execute all the auto and manual tests:
testkit-lite -f tests.xml -A
8. If you just want to execute the significant tests:
testkit-lite -f tests.xml -S
9. If you want to choose some filters:
testkit-lite -f tests1.xml tests2.xml --level level1 level2 --type type1 type2 --Ntestcase gfx1 gfx2...
Note that the test cases will be filtered out by both black rules and white rules.

10. At last, you can freely compose the above paramters together:
testkit-lite -f tests1.xml tests2.xml --testxmlconfig config1 config2 -D -A -S -C --level level1 level2 --type type1 type2 ...
11. One more parameter is prepared for customized compatible mode for test report:
testkit-lite -f tests.xml -C
12. Notes:

testkit-lite enables only automatic tests by default. Obviously -A and -M are conflict options.

==== How to get result ====
1. testkit-lite's TestLog is stored to /opt/testkit/lite/latest after execution, you can also check the history results in /opt/testkit/lite/yyyy-mm-dd-HH:MM:SS.NNNNNN.

2. Two kinds of test report will be generated:

1)<tests xml name>.textresult, e.g.

[[File:image011.jpg|400px]]

2)<tests xml name>.xmlresult

xml result files aligned with schema files: /opt/testkit-lite/xsd/testdefinition-results.xsd, e.g.

[[File:image012.jpg|800px]]

Detail Options of testkit-lite:

[[File:image013.jpg|400px]]

Quality/QA-tools

2011-06-20T13:33:54Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

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

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

 
[[Category:QA]]

Quality/QA-tools

2011-06-20T13:32:31Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device tool for sending core dumps to core dump data base
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|-
| [[Quality/QA-tools/CrashReports|Crash Reports Web UI]] || Web UI for Crash Reports
|-
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance
|-
| Application Monitor || Monitor runtime indicators - CPU, memory, power for specified apps
|-
| Video performance || Collect FPS, CPU information when do video playback
|-
| [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || Test cases and Cucumber steps for MeeGo QML UI applications
|}

'''Other utilities'''

{| border="1" cellspacing="0"
|+
|'''Name (link to wiki page)''' ||'''Short description'''
|-
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files
|-
| [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages
|-
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] ||
|-
| [[Quality/QA-tools/rich-core|Rich core dumper (sp-rich-core)]] || A tool to collect core dump and context data from process crashes
|-
| Crash Reporter settings || Settings package for Crash Reporter
|-
| [[Quality/QA-tools/hat-control|Hardware Accessory for Testing (HAT)]] ||
|-
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] ||
|-
| Service OS based Flasher || Flasher to support Intel netbook/tablet
|-
| Environment collector || Collect detail system environment information
|-
| [[Quality/QA-tools/Corelysis|Corelysis]] || A daemon to process rich core dumps in the back-end server
|-
| [http://wiki.meego.com/Testkit_Howto testkit-lite] || python based test framework, command line tool, supporting test definition xml
|-
| [http://wiki.meego.com/Testkit_Howto testkit-manager] || web based test tool with fancy UI, supporting both manual and auto testing remotely
|}

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

 
[[Category:QA]]

Quality/QA-tools

2011-05-17T02:16:57Z

Jwang: /* Tools and other utilities */

= Quality assurance (QA) tools =

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

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

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

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

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

== Overview ==

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

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

== Tools and other utilities ==

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

'''Test tools'''

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

{| border="1" cellspacing="0"
|+
|'''Tool (link to wiki page)''' ||'''Short description'''
|-
| Crash Reporter || On-device tool for sending core dumps to core dump data base
|-
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system
|-
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution
|-
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing
|-
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports
|-
| [[Quality/QA-tools/CrashReports|Crash Reports Web UI]] || Web UI for Crash Reports
|-
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance
|-
| Application Monitor || Monitor runtime indicators - CPU, memory, power for specified apps
|-
| Video performance || Collect FPS, CPU information when do video playback
|}

'''Other utilities'''

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

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

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

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

== Feature requests and bugs ==

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

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

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

== Collaboration spaces ==

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

== Nice to have ==

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

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

 
[[Category:QA]]

Quality/QA-tools/Meetings

2011-05-10T07:59:11Z

Jwang: /* Next meeting */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday May 10th 2011 08:00 UTC''' - Agenda Proposal

* Actions from the previous meeting
* Latest Tools Status
* Any Other Business
* http://testdata.meego.com/ ---- need to upload license file and confirm with license.this website get from mcts-mwts-gstreamer testing suite readme. but don't find the license doc in this website.
* MeeGo Conference attendance and topic (jwang)

== Previous Meeting Minutes ==

'''Tuesday May 3rd 2011 08:00 UTC'''

* General QA tools status update and priorities of new development
* Restructuring QA tools wiki page
* Latest Tool Status
* Any Other Business

[http://irclogs.meego.com/meetbot/meego-meeting2/2011/meego-meeting2.2011-05-03-07.59.html Minutes]

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quality/QA-tools/Meetings

2011-04-27T08:38:30Z

Jwang: /* Next meeting */

= QA Tools - Weekly Meetings =

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

== Next meeting ==

'''Tuesday May 3rd 2011 08:00 UTC''' - Agenda Proposal * Restructure QA tool page * Latest Tool Status

* QA tools status update
* Any Other Business

== Previous Meeting Minutes ==

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

* Regular Meeting Agenda

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-01-29T10:40:25Z

Jwang: /* OTS server installation */

= OTS 0.8.x installation =

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

All OTS machines need to be able to access other OTS machines based on their hostname.

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[http://wiki.meego.com/Quality/QA-tools/OTS/Plugins/HTTP_logger Logger plug-in] (recommended)
[http://wiki.meego.com/Quality/QA-tools/OTS/Plugins/Email Email plug-in] (recommended)

See more plug-ins from [http://wiki.meego.com/Quality/QA-tools/OTS/Plugins OTS Plug-ins]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Change permissions to OTS worker log
sudo chown <user>:<group> /var/log/ots.log

* Start OTS worker
ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Install dependencies
sudo apt-get install meego-ai-flaster eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* If you want run ots_worker as user, copy SSH keys to the user and make udev rule for n900
install-eat-key.sh
sudo nano /etc/udev/rules.d/meego-n900.rules
SUBSYSTEMS=="usb", ATTR{idVendor}=="0421", ATTR{idProduct}=="0105", GROUP="<group>", MODE="0664"

* Create a power_cycle.sh script for turning N900 on/off. This requires external accessory, like [http://wiki.meego.com/Quality/QA-tools/hat-control HAT]
sudo nano /usr/bin/power_cycle.sh

#!/bin/bash

hat_drv &
hat_ctrl -pwr1=off
hat_ctrl -usb1data=off
hat_ctrl -usb1pwr=off
sleep 2;
hat_ctrl -usb1pwr=on
hat_ctrl -usb1data=on
hat_ctrl -pwr1=on
killall hat_drv

* Test manually that everything is OK, this is executed in the worker
conductor -u <image url>
* Start OTS worker
ots_worker

Quality/QA-tools

2010-12-27T01:21:38Z

Jwang: /* Tools and Maintainers */

= 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 [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://meego.gitorious.org/meego-quality-assurance/ git repositories] and create merge request. Tool maintainers in our projects will review your contributions and decide on merge.

'''Targets:'''

* Improve MeeGo test reporting tools - target from MeeGo Quality Assurance
* 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."

== Tools and Maintainers ==

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

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

The maintainer of the tree shall update the changelog.

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

You can install Testrunner UI, testrunner-lite, Testplanner, OTS, Meego-ai and eat from Tools:Testing repository. The instructions for setting up the repositories can be found [[Quality/QA-tools/How_to_set_up_repositories|here]].

See the rest of our team members and our collaboration spaces [[Quality/QA-tools#Team_Members_and_Collaboration_Spaces|below]]. If you are interested in the user experience work regarding these tools, you can find more information [[Quality/QA-tools/User experience|here]].

=== Overview ===

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

[[File:testautomationtools.png]]

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

== Release Practices ==

Here's the workflow for QA-tools release practices.

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

[[File:Release.png]]

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

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

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

''' YouTube videos '''

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

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

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

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

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

== Features and Bugs ==
Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=ASSIGNED&component=eat&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=testrunner%20UI&component=testrunner-lite&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=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=testrunner%20UI&component=testrunner-lite&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order]

Bugzilla workflow: [[Bugzilla/how-report-bugs]]

== Documentation ==

This section will contain links to various guides and user documentation. See [[Quality/QA-tools#Tools_and_Maintainers|the wiki pages of the tools]] for tool-specific documentation.

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

== Design/ Planning ==

* [[Quality/QA-tools/MCTS-Test-Automation-Design|MCTS Test Automation]] (QA Tools support for MCTS) '''WORK IN PROGRESS'''

== Meetings ==

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

=== Team meetings ===

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

* [[Quality/QA-tools/Meetings|Meeting agendas and minutes]]

=== Architecture meetings ===

Architecture meetings will be held on-demand basis i.e. when topics do not fit in QA-Tools weekly meeting time frame.

* [[Quality/QA-tools/Arch-Meetings|Meeting agendas and minutes]]

=== Workshops ===

Face-2-face meetings within the team.

* [[Quality/QA-tools/Workshops|Meeting agendas and minutes]]

== Team Members and Collaboration Spaces==

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

{| border="1" cellspacing="0"
|+
| '''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
|-
| Elias Luttinen || Team member || Digia || eluttine
|-
| Ville Niutanen || Team member || Digia || Villen
|-
| Esa-Pekka Miettinen || Team member || Digia || E-P
|-
| Vesa Poikajärvi || Team member || Digia || vesse
|-
| 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 || -
|-
| Alexey Kuznetsov || Team member || Digia || alkuznet
|-
| Sergey Timofeev || Team member || Digia || setimofe
|-
| Daniil Chuiko || Team member || Digia || dachuiko
|-
| Jarno Keskikangas || Team member || Leonidas || jakeskik
|-
| Janne Hietamäki || Team member || Leonidas || _janne
|-
|}

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

[[Category:QA]]

Quality/QA-tools/PXEInstall

2010-09-14T06:37:24Z

Jwang:

* Make sure the package for TFTP server is installed.
* Prepare the directory and PXE boot loader for TFTP server
[root@meego-global ~]#mkdir /tftpboot/
[root@meego-global ~]#cp /usr/lib/syslinux/pxelinux.0 /tftpboot
* Setup boot configuration file
[root@meego-global ~]#mkdir / tftpboot/pxelinux.cfg
[root@meego-global ~]#vi / tftpboot/pxelinux.cfg/[[mac_address]]

The configuration file is sth like
default local
prompt 1
timeout 5
display boot.msg
label local
localboot 0
label installer
kernel xxxx
append initrd=xxxx

* Configure tftp service through xinet
Edit /etc/xinetd.d/tftp as below
service tftp
{
disable = no #enable the tftp server
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot #set the tftp root dir is /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}

* Enable auto start the tftp server when next time system reboot
[root@meego-global ~]# ntsysv

* Install PXE kernel and initrd
For Fedora, there is existing PXE boot kernel and initrd, just use them. But for meego, you need create by yourself. Definitely you can refer to Fedora. Make sure path is consistent with pxe configuration file

Quality/QA-tools/PXEInstall

2010-09-14T06:36:57Z

Jwang:

* Make sure the package for TFTP server is installed.
* Prepare the directory and PXE boot loader for TFTP server
[root@meego-global ~]#mkdir /tftpboot/
[root@meego-global ~]#cp /usr/lib/syslinux/pxelinux.0 /tftpboot
* Setup boot configuration file
[root@meego-global ~]#mkdir / tftpboot/pxelinux.cfg
[root@meego-global ~]#vi / tftpboot/pxelinux.cfg/[[mac_address]]

The configuration file is sth like

default local
prompt 1
timeout 5

display boot.msg
label local
localboot 0

label installer
kernel xxxx
append initrd=xxxx

* Configure tftp service through xinet
Edit /etc/xinetd.d/tftp as below
service tftp
{
disable = no #enable the tftp server
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot #set the tftp root dir is /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}

* Enable auto start the tftp server when next time system reboot
[root@meego-global ~]# ntsysv

* Install PXE kernel and initrd
For Fedora, there is existing PXE boot kernel and initrd, just use them. But for meego, you need create by yourself. Definitely you can refer to Fedora. Make sure path is consistent with pxe configuration file

Quality/QA-tools/PXEInstall

2010-09-14T05:44:56Z

Jwang:

* Make sure the package for TFTP server is installed.
* Prepare the directory and PXE boot loader for TFTP server
[root@meego-global ~]#mkdir /tftpboot/
[root@meego-global ~]#mkdir / tftpboot/pxelinux.cfg
[root@meego-global ~]#cp /usr/lib/syslinux/pxelinux.0 /tftpboot

* Configure tftp service through xinet
Edit /etc/xinetd.d/tftp as below
service tftp
{
disable = no #enable the tftp server
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot #set the tftp root dir is /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}

* Enable auto start the tftp server when next time system reboot
[root@meego-global ~]# ntsysv

* Install PXE kernel and initrd
For Fedora, there is existing PXE boot kernel and initrd, just use them. But for meego, you need create by yourself. Definitely you can refer to Fedora.

Quality/QA-tools/PXEInstall

2010-09-14T05:42:37Z

Jwang:

* Make sure the package for TFTP server is installed.

* Prepare the directory and PXE boot loader for TFTP server
[root@meego-global ~]#mkdir /tftpboot/
[root@meego-global ~]#mkdir / tftpboot/pxelinux.cfg
[root@meego-global ~]#cp /usr/lib/syslinux/pxelinux.0 /tftpboot

* Configure tftp service through xinet
Edit /etc/xinetd.d/tftp as below
service tftp
{
disable = no #enable the tftp server
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot #set the tftp root dir is /tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}

* Enable auto start the tftp server when next time system reboot
[root@meego-global ~]# ntsysv

* Install PXE kernel and initrd

Quality/QA-tools/PXEInstall

2010-09-14T05:39:27Z

Jwang: Created page with "* Make sure the package for TFTP server is installed. * Prepare the directory and PXE boot loader for TFTP server * Configure tftp service through xinet * Enable auto start t…"

* Make sure the package for TFTP server is installed.

* Prepare the directory and PXE boot loader for TFTP server

* Configure tftp service through xinet

* Enable auto start the tftp server when next time system reboot

* Install PXE kernel and initrd

Quality/QA-tools

2010-09-14T05:35:43Z

Jwang: /* Team Members */

== 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 [http://meego.com/about/contribution-guidelines MeeGo contribution guidelines]. In addition, you may take personal clone from our [http://gitorious.org/qa-tools 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 [http://wiki.meego.com/index.php?title=Quality/QA-tools&action=submit#Tuesday_August_31th_2010_12:00_UTC_-_Meeting_agenda_and_minutes 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 [http://meego.com/about/contribution-guidelines 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?

{| border="1" cellspacing="0"
|+
| Tool
| Maintainer
| IRC nick
|-
| [http://gitorious.org/qa-tools/test-definition test-definition] || Sampo Saaristo || samposa
|-
| [http://gitorious.org/qa-tools/testrunner-lite testrunner-lite] || Sampo Saaristo || samposa
|-
| [http://gitorious.org/qa-tools/eat eat - enables automated testing] || Timo Härkönen || timoph
|-
| [http://gitorious.org/qa-tools/ots ots - open testing system] ||Teemu Vainio ||tvainio
|-
| [http://gitorious.org/qa-tools/testrunner-ui testrunner user interface] || Kyösti Ranto || kyranto
|-
| [http://gitorious.org/qa-tools/mcts MeeGo Core Test Suite] || Matti Salmi and Jeff Zheng || N/A and xzheng
|-
| [http://gitorious.org/qa-tools/mnts MeeGo Netbook Test Suite] || Jeff Zheng || xzheng
|-
| [http://gitorious.org/qa-tools/qtuitest-mbt-adapter Model-Based Testing adapter for qtuitest] || Riku Halonen || rikhalon
|-
| [http://gitorious.org/min MIN test framework] || Sampo Saaristo || samposa
|}

Team communication is in English and takes place on [http://webchat.freenode.net/?channels=meego-qa-tools #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 [http://wiki.meego.com/Quality/QA-tools/User_Experience 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? - [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools Please do it here]

* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_severity=enhancement&bug_status=ASSIGNED&component=eat&component=min&component=testdefinition&component=testrunner%20UI&component=testrunner-lite&classification=MeeGo%20Platform&product=Development%20Tools Assigned enhancemens - Working on it]
* [http://bugs.meego.com/buglist.cgi?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=ots&component=testdefinition&component=testrunner%20UI&component=testrunner-lite&product=Development%20Tools&classification=MeeGo%20Platform All open enhancements and bugs in priority order]

=== Meetings ===

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

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

* 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 - Meeting agenda and minutes ====

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

=== Team Members ===

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

{| border="1" cellspacing="0"
|+
| 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:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
** Please also poke team members or Ville Ilvonen either by email or on IRC because of high traffic @ meego-dev
* [http://webchat.freenode.net/?channels=meego-qa-tools #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
* [http://wiki.meego.com/Quality/QA-tools/ServiceOS ServiceOS]
* [http://wiki.meego.com/Quality/QA-tools/PXEInstall PXEInstallation]

[[Category:QA]]

Quality/QA-tools

2010-07-31T09:23:51Z

Jwang: /* QA Tools */

== Quality Assurance (QA) Tools ==

Quality Assurance tools are developed to ensure MeeGo SW quality.

Work in progress includes open sourcing Nokia / Intel quality assurance tools and making open source test tools available for anyone interested in MeeGo software quality.

== QA Tools ==

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

QA tools team develops and maintains tools for Quality Assurance.

Anyone is welcome to contribute and non-member contributions will be treated
with same process and review as member contributions.

Summer 2010: We are in the process of making Nokia and Intel QA tools available for MeeGo. Please bear with us.

Team communication is in English.

Team meetings will be held in <code>#meego-meeting on irc.freenode.net</code> starting September - '''Meeting time has not been fixed - proposals welcome'''

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

{| border="1" cellspacing="0"
|+
| Name
| Role
| Affiliation
| IRC nickname
|-
| Ville Ilvonen || Team lead (act.) || Nokia || vilvo
|-
| Riku Halonen || Team member || Nokia || rikhalon
|-
| Kari Sievi || Team member || Digia || -
|-
| Timo Härkönen || Team member || Digia || timoph
|-
| Carol Rus || Team member || Digia || -
|-
| Sami Lahtinen || Team member || Digia || -
|-
| Raimo Gratseff || Team member || Digia || -
|-
| Sampo Saaristo || Team member || Sofica || -
|-
| Ling Yu || Team member || Intel || -
|-
| Jing Wang || Team member || Intel || -
|-
|}

Our collaboration spaces are:

* [http://lists.meego.com/listinfo/meego-dev meego-dev@meego.com mailing list], please prefix with 'QA-tools' for team related topics.
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net]
* Gitorious team, http://gitorious.org/qa-tools (to be moved meego.gitorious.org)
* MeeGo OBS
* This wiki area
* [http://wiki.meego.com/Quality/QA-tools/ServiceOS ServiceOS]

[[Category:QA]]

Quality/QA-tools

2010-07-31T09:23:24Z

Jwang: /* QA Tools */

Quality/QA-tools/Targets

2010-07-31T09:22:08Z

Jwang: /* Open tasks */

== Target ==

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

Target is to support above testing with automated test execution.

== Open tasks ==

All open QA-tools tasks are in [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]

== Targets mapped to [[Release_Engineering/Plans/1.1|Release Iterations]] ==

=== Release Iteration 1.0.80.13 / 2010-07-29--2010-08-04 ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description !! Start !! End !! Responsible
|-
| N/A
| N/A
| N/A
| N/A
| N/A
|}

=== Release Iteration 1.0.80.14 / 2010-08-05--2010-08-11 ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description !! Start !! End !! Responsible
|-
| N/A
| N/A
| N/A
| N/A
| N/A
|}

Quality/QA-tools/ServiceOS

2010-07-31T09:21:17Z

Jwang: Created page with '== What's Service OS (SOS) == Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific s…'

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific script upon, it can achieve various of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root file system from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
fdisk -u -C$C -H$H -S$S $loopdev <<EOF
n
p
1
a
1
p
w
EOF

* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

Quality/QA-tools

2010-07-31T09:20:17Z

Jwang: /* QA Tools */

Quality/ServiceOS

2010-07-31T09:17:45Z

Quality/QA-tools

2010-07-31T09:17:25Z

Jwang:

ServiceOS

2010-07-31T09:15:04Z

Jwang: /* Create bootable SOS image */

ServiceOS

2010-07-31T09:14:39Z

Jwang:

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific script upon, it can achieve various of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root file system from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
fdisk -u -C$C -H$H -S$S $loopdev <<EOF
n
p
1

a
1
p
w
EOF

* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

ServiceOS

2010-07-31T09:12:11Z

Jwang: /* Create SOS file system */

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific script upon, it can achieve various of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root file system from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

ServiceOS

2010-07-31T09:11:34Z

Jwang: /* Create SOS file system */

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific script upon, it can achieve various of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root filesystem from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

ServiceOS

2010-07-31T09:11:12Z

Jwang: /* What's Service OS (SOS) */

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot target platform individually. By combined with specific script upon, it can achieve various of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root filesystem from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

ServiceOS

2010-07-31T09:10:44Z

Jwang: /* What's Service OS (SOS) */

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot
target platform individually. By combined with specific script upon, it can achieve various
of purposes. Typical usage is on automated testing system, help do image auto-installation,
HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root filesystem from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]

ServiceOS

2010-07-31T09:10:05Z

Jwang: /* What's Service OS (SOS) */

== What's Service OS (SOS) ==
Service OS is small Linux os which resides on USB/SDHC or hard disk partition. It can boot
target platform individually. By combined with specific script upon, it can achieve various
of purposes. Typical usage is on automated testing system, help do image auto-installation, HW health check.

== Create SOS file system ==
Root file system of SOS can be gotten from any Linux Distros - Fedora, Ubuntu, MeeGo, etc. Below is a way to create SOS root filesystem from MeeGo
* Download image-creator tool from http://meego.gitorious.org/meego-developer-tools
* Create a .ks config file which include all rpm groups or packages you want.
* Create image by command such as
mic-image-creator --record-pkgs=name -P $prefix -S $suffix -c ./sos.ks -f loop --cache=./mycache
* File system is in loop image file, do some tweaks before tarball
Mount fs: mount -o loop ${prefix}-meego-${suffix}.img $pmnt
Adjust run level: sed -i 's/id:5/id:3/' $pmnt/etc/inittab
Create grub configure file based on kernel and initrd under /boot

== Create bootable SOS image ==
Assuming we have gotten root file system in last section as rootfs.tgz
* Create empty image file
dd if=/dev/zero of=$IMGFILE bs=512 count=$SECTORS
* Associate the image to free loop device
losetup $loopdev $IMGFILE
* Create a partition and its mapping
* Format the partition
mkfs.ext3 /dev/mapper/$part_name
* Copy whole root file system into image
mount /dev/mapper/$part_name $pmnt
tar vxf $FS -C $pmnt/
* Install grub
grub --batch --no-floppy <<EOF
device (hd0) $loopdev
root (hd0,0)
setup --stage2=$pmnt/boot/grub/stage2 (hd0)
EOF
* A bootable image is done.
dd if=serviceos.IMG of=/dev/[USBDevice]