Information on the QA project and team.

QA Team


What does the QA team do?

Note that the QA team is not itself responsible for fixing bugs, this is the task of the developers. The QA team maintains the OGo Bugzilla, eg by creating a weekly bugreport, ensures that bugs submitted can be reproduced (therefore lower the test burden on the developers) and ensures that bugs marked fixed by a developer really work.
The QA team is also responsible for creating and performing standardized tests (eg click tests) as well as checking whether patches provided by non-core contributors work at all and whether those patches comply with the basic OGo styleguides.

The QA has direct contact to the project leads (currently just Helge) for coordination. Note that the leads have the last word regarding bug priority or severity settings.

Mailinglist

For now the QA team will use the developer@opengroupware.org mailing list. QA related mails will be prefixed with a "[QA]: " in the mail subject.
In case the list traffic gets too high, we are going to create a separate QA list.

  • subscribe
  • archives

    • Update: 2004-04-01

    The QA team around Matthias, Sebastian and Bjoern is being set up. Matthias already started on a draft of a bug overview document.

    Bugzilla

    write something ...

  • OGo Bugzilla

    • Workflow

    write something ..., draft:

    1. Bug kommt rein => NEW status
    2. QA Team schaut sich Bug an => ASSI
      - versucht zu reproduzieren
      - wenn als gueltig bewertet => REASSI an Coder
    3. Coder ASSI
      - fixt
    4. Coder CLOSED, RAWHIDE
    5. QA Team schaut sich Bug an
      - testet Fix
      - wenn als gueltig bewertet => CLOSED, RELEASE?
      - ansonsten REOPEN, gehe ueber 3.

    We already found in flaw in that the RedHat Bugzilla as used in OGo doesn't provide a separate state for "verified" and once a bug is marked RAWHIDE it can only be reopened or commented.
    So we are probably are going to use a keyword to mark bugs as verified.