I think we should put something like this at some visited place: We would like to help you, but we are very busy. We answer e-mails inour free time, so please help us help you. We will first answere-mails that follow this simple rules. >From The Basics of Bug Tracking (FogBugz Documentation): Every good bug report needs exactly three things.1. Steps to reproduce,2. What you expected to see, and3. What you saw instead. We should also add: 4. Please provide your script and html. Please make it as short aspossible. Remove all code and html that is not necessary to reproducethe problem.5. Please search mail archive and faq. Your problem may be alreadysolved. Wa are very sad when we see a question that is alreadyanswered (and we can not answer your question with eyes full oftears). If you find an answer in mail archive and not in faq, pleaseadd it to faq. We should also link to http://www.catb.org/~esr/faqs/smart-questions.html I am not a native speaker. I tried to use style that is friendly, butI am not shure if I did a good job. On 3/17/06, Bret Pettichord <[EMAIL PROTECTED]> wrote:>> Frankly i have been surprised at how poor many of the bug reports on this list have been. They routinely omit key information.>> For a while, i thought that testers knew how to write good bug reports, but i actually see better bug reports on the mailing lists for open-source developer tools. Are developers better than testers are reporting problems?>> I'm considering refusing to try and speculate and suggest possible solutions when reports fail to provide the full error information and actual scripts. And i'm considering asking the other active answer providers on this list (like Zeljko and Michael and Chris) to follow the same policy.>> Now that the web recorder has lowered the bar for many people to start using Watir, i'm thinking we need to raise the bar for what information needs to be provided to get out attention.>> Comments please. It's been a very busy week at work and i'm tired and am unsure of my judgement ! here. Does this sound reasonable?>>> Bret>> _______________________________________________> Wtr-general mailing list> [email protected]> http://rubyforge.org/mailman/listinfo/wtr-general>>
--http://www.testingreflections.com/blog/3071http://iskusivac.blog.hr/ _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
