(was [qa-dev] [Automation]questions/announcements regarding automation)
Hi Andre,
André Schnabel wrote:
Hi Helge,
Helge Delfs schrieb:
-1 for tagging in IssueTracker, as the tag is redundant (as far as I
can see).
Btw - it is sad, that we have no summary of the most recent IRC
QA-Session. The problem that we encountered there was, that the
This was the second chat and all are in the learning phase. So if
highlights of the chats should be documented, they should be collected
on the wiki page for the chat - my proposal.
description of verified issues was often not very clear and not easy to
reproduced. This was caused by the fact hat these have been submitted by
long term qa members directly to the developer. As they often work next
door, they rather talk about the problem, than file a proper issue. This
might speed up the process for those two - but other volunteers are los.
Means, volunteers have hardly a chance to help.
I am on your side. This shouldn't be the case. The QA team should write
a description which should be reproducible by anyone. And when somebody
else has written an issue a reproducible scenario has to be written down
in the issues. That was decided for my team long time ago. Especially
because everybody have to understand the issue. Otherwise the chats
doesn't make sense.
On the wiki-page for the chats you can find the names of the QA persons
in the Sun team. When an issue is checked by one of these guys the
issues should have a good summary. But there are also so called
developer tasks/issues. They checked the issues by themselves and they
are often too complicated for QA persons. Therefore this point was
added to the hints for chat.
But I will remember the team to summaries and clean up the descriptions
for an issue, that the QA community can easier reproduce the issues.
Thanks for the hint.
Thorsten
wiki-page : http://wiki.services.openoffice.org/wiki/Issue_hunting_party
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
