Meego Wiki
Views

Quality/QA-tools/Arch-Meetings

From MeeGo wiki
< Quality | QA-tools(Difference between revisions)
Jump to: navigation, search
 
(17 intermediate revisions not shown)
Line 1: Line 1:
 +
== Meeting Intent ==
 +
 +
Meeting purpose is to solve QA Tools related issues, which need an architectural level decision within the team. For example, a developer working in QA Tools team can propose topics to be reviewed. These meetings are being held on a need basis, approximately once or twice a month, in '''#meego-meeting'''. Depending the amount of topics. 
 +
 +
'''Note:''' Primary channel for tools related issues is still '''#meego-qa-tools'''.
 +
 +
== Meeting Topics Backlog ==
 +
 +
[Add topics here with your IRC nick and bugzilla item (if available)]
 +
== Next Meeting ==
== Next Meeting ==
-
'''Background:'''
+
Not scheduled.
-
BLTS/ MWTS has a requirement to execute test cases automatically in OTS environment. This sets new challenges for the environment, as multiple devices are needed to controlled within a test run. In this meeting we'll sync what's current ongoing in this area and plan the common way how to go forward with this.
+
== Meeting Minutes ==
-
* http://bugs.meego.com/show_bug.cgi?id=9886
+
'''February 10th 2011 11:00 UTC'''
-
* http://wiki.meego.com/User:Esmietti
+
 
 +
'''Reviewed topics:'''
 +
 
 +
* TestCaseTemplate alignment with testdefinition (https://bugs.meego.com/show_bug.cgi?id=11253):
 +
** The purpose of TC_ID, TC_TITLE vs. testdefinition name field. The uniqueness of TC_ID field.
 +
** Description field syntax when supporting TestCaseTemplate.
 +
 
 +
* Is there really need for support for <environment> tag in Testplanner and Testrunner(ui). It's needed for backward compatibility in testrunner-lite.
 +
 
 +
* N/A result interpretation
 +
** How is the N/A handled by ots result judge; and on low level: N/A test step effect on case result (https://bugs.meego.com/show_bug.cgi?id=12378)
 +
** Are filtered cases N/A ?(https://bugs.meego.com/show_bug.cgi?id=5978)
 +
 
 +
* "Testplanner/Testrunner merge" - with integration to QtCreator and workflow redesign (items in bugzilla) this makes sense to discuss.
 +
 
 +
[[http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-10-10.58.html Meeting minutes]]
 +
 
 +
----
 +
 
 +
'''November 24th 2010 12:00 UTC'''
'''Agenda:'''
'''Agenda:'''
Line 14: Line 43:
* OTS integration
* OTS integration
* Plan forward
* Plan forward
-
+
 
-
== Meeting Minutes ==
+
[[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-24-11.59.html Meeting minutes]]

Latest revision as of 12:51, 10 February 2011

Contents

Meeting Intent

Meeting purpose is to solve QA Tools related issues, which need an architectural level decision within the team. For example, a developer working in QA Tools team can propose topics to be reviewed. These meetings are being held on a need basis, approximately once or twice a month, in #meego-meeting. Depending the amount of topics.

Note: Primary channel for tools related issues is still #meego-qa-tools.

Meeting Topics Backlog

[Add topics here with your IRC nick and bugzilla item (if available)]

Next Meeting

Not scheduled.

Meeting Minutes

February 10th 2011 11:00 UTC

Reviewed topics:

  • TestCaseTemplate alignment with testdefinition (https://bugs.meego.com/show_bug.cgi?id=11253):
    • The purpose of TC_ID, TC_TITLE vs. testdefinition name field. The uniqueness of TC_ID field.
    • Description field syntax when supporting TestCaseTemplate.
  • Is there really need for support for <environment> tag in Testplanner and Testrunner(ui). It's needed for backward compatibility in testrunner-lite.
  • "Testplanner/Testrunner merge" - with integration to QtCreator and workflow redesign (items in bugzilla) this makes sense to discuss.

[Meeting minutes]

November 24th 2010 12:00 UTC

Agenda:

  • Current status
  • Architecture proposal(s)
  • OTS integration
  • Plan forward

[Meeting minutes]

Retrieved from "http://wiki.meego.com/Quality/QA-tools/Arch-Meetings"
Personal tools