Joost Andrae wrote:
Hi,
this is a good description of the oooqa keyword usage. More
information about the keywords can be read here:
http://qa.openoffice.org/issues/describekeywords.cgi
I as qa volunteer how can/shold use oooqa keyword?
You should use it. It signals: "This issue already has been gone
through a first review" - either with the restult that the description
is clrearly understandable, that all required sample documents are
available, that the subject is telling, that the other flags are set
properly.
And: You should have checked for duplicates (often this is forgotten,
and I blame myself here as well)
Sum-up: Any issue with oooqa (and no needmoreinfo) keyword should meet
the minimum requirements of an issue.
This is at least my interpretation of the keyword.
Hi,
Zoltan, thanks for asking this question.
For sure I do not make efficient, or even proper, use of keywords.
Let me pose a few scenarios with regard to this keyword then, if I may?
Use Case 1: The volunteer has canconfirm privileges.
They have reviewed an issue, found it to be 'well formed' (clear
description, required docs, etc). It would seem that there are three
possible action scenarios at this point.
1] They can reproduce the behavior. The issue should be set to NEW.
Adding the keyword oooqa seems redundant at this point.
2] They can not reproduce the behavior. In this case they should add a
comment to this effect and ask the reporter for clarification.
Add keywords oooqa and needmoreinfo? Again though oooqa seems a bit
redundant, but perhaps less so.
3] They can not attempt to reproduce the behavior for some reason.
(maybe it is reported for the Mac and they do not have a Mac)
Add keyword oooqa. But should they also add 'needhelp'?
Use Case 2: The volunteer does not have canconfirm privileges.
They have reviewed an issue, found it to be 'well formed' (clear
description, required docs, etc).
They set the keyword oooqa.
Are those use cases about what is being envisioned here?
Can someone without canconfirm actually add keywords?
Thanks
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
