Quality/QA-tools/Arch-Meetings

Revision as of 15:48, 8 February 2011

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

• When: Thursday, 10th of Feb 2011 at 11:00 UTC
• Where: #meego-meeting
• Duration: 1 hour

Topics to review

• 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.

Meeting Minutes

Wednesday November 24th 2010 12:00 UTC

Agenda:

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

[Meeting minutes]