Hi André,

André Schnabel wrote:
Why need issues regarding automation no detailed description? To me as a volunteer (who is still somehow interested in automation) it is important to quickly find issues in Issue Tracker. Best mean for this is the summary.

With [automation] tag quicker to be found in the future ;-)

Ok - if issues for automation are only used by experienced automation team members (who know the topic of the issue anyway) you do not need a good description.

A detailed description must not be a good description.

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 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 theprocess for those two - but other volunteers are los. Means, volunteers have hardly a chance to help.

I think we don't need the log of the recent QA-Session as it is our daily job to handle these problems and I know hat you're talking about. If the description to reproduce an issue is not detailed enough even a well experienced QA member has problems to reproduce this. But we shouldn't mix the things: To reproduce an issue in automated scripts or an issue found by scripts you simply have to read the code or start the script, thats the way you have to reproduce it, no deep detailed description is needed here. If issue holds the name of the script and the testcase/function/sub the error occurs and what kind of error occurs everybody who is able to run automated tests can reproduce this.

At the moment I feel, automation team is going exactly the same route.

Recheck your feelings if you compare the 'quality' of issues to be submitted if they have to be reproduced manualy or with an automated script in hands.


--
Regards
 Helge



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to