In general, what you need for each bug report is: 1- A statement of the bug (e.g. "Received null object error from Account Maintenance screen.") 2- A list of steps for reproducing (e.g. "Press Apply, then Cancel on the Account Maintenance screen after filling out the name field.") 3- A statement of expected behavior 4- Any additional relevant info (e.g. version of the software, etc..)
If you have a set list of requirements off of which dev and testing is done, then the corresponding requirement number is useful as well. Jacob A. Grass Presentation Team Lead Viziqor ______________________ this message contains confidential information intended solely for the recipient of the addressee(s) named above any review disclosure distribution copying or use of the information by others is strictly prohibited if you have received this message in error please advise the sender by immediate reply and delete the original message > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Erick Thompson > Sent: Thursday, July 07, 2005 12:52 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] FAQ/guidance for testers > > Paul, > > I can't disagree with you on this one. The problem is, we're > a non-profit, and not even a computer focused non-profit. So > the people that I get working for me are generally interns, > but from a poly-sci background. Very sharp and motivated > people, but this is an area in which they have no expertise, > and don't know what is useful feedback/bug reporting. I'm > having to make do with what I have. > > Thanks, > Erick > > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Mehner > Sent: Wednesday, July 06, 2005 5:03 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] FAQ/guidance for testers > > I'm bringing a couple of new people onto my construction > project as electricians. They are not familiar at all with > electrical work and they aren't really certain what they > should be doing, and how they should be doing it. Does anyone > know of a good summary/how-to for electricians to get them > started? I'm thinking of basic stuff like how to identify > wires, circuit breakers, and electrocution avoidance. > > Sorry Erick... I couldn't resist poking a little fun at your expense. > It's not really fair of me because I don't know your > specifics. It is simply ironic to me that practices that are > unacceptable (for good > reason) in almost all other established lines of business are > too often encouraged in our own. > > Please take my light-hearted humor in fun! I simply meant to > illuminate the irony of hiring non-qualified testers. In all > seriousness, I recommend abandoning your plan to just bring > new people onto your project and hire qualified testers as it > is presumed that you expect to receive some reasonably > proportionate value out of their employment. At the very > least hire college students (even a high school student) with > some level of software testing training. The quality of your > software testing will be directly reflected in the knowledge > and experience of your testers. > > --Paul Mehner > > > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Erick Thompson > Sent: Wednesday, July 06, 2005 3:28 PM > To: [email protected] > Subject: [ADVANCED-DOTNET] FAQ/guidance for testers > > Good afternoon everyone, > > I'm bringing a couple of new people into a project as > testers. They are not familiar with testing at all, and > aren't really sure what they should be doing, and how they > should be doing it. Does anyone know of a good summary/how-to > for testers? I'm thinking about basic stuff like what you > need to report, how to report it (high level - e.g., not > verbal), what is useful and what isn't, etc. > > Thanks! > > Erick > > > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
