This link has been bookmarked by 104 people . It was first bookmarked on 07 Sep 2006, by Jean Loup.
-
05 Jun 15
-
01 Jun 15
-
26 Feb 15
-
26 Jan 15
-
21 Dec 13
-
reduce the repro steps to the minimal steps to reproduce
-
Anyone can resolve it
-
only the person who saw the bug can really be sure that what they saw is fixed
-
keep careful track of versions
-
just don't accept bug reports by any other method
-
don't tell them about bugs - put them in the database and let the database email them
-
-
16 Jul 13
-
- Steps to reproduce,
- What you expected to see, and
- What you saw instead.
It's pretty easy to remember the rule for a good bug report. Every good bug report needs exactly three things.
Seems easy, right? Maybe not. As a programmer, people regularly assign me bugs where they left out one piece or another.
-
- A good tester will always try to reduce the repro steps to the minimal steps to reproduce; this is extremely helpful for the programmer who has to find the bug.
- Remember that the only person who can close a bug is the person who opened it in the first place. Anyone can resolve it, but only the person who saw the bug can really be sure that what they saw is fixed.
- There are many ways to resolve a bug. FogBUGZ allows you to resolve a bug as fixed, won't fix, postponed, not repro, duplicate, or by design.
- Not Repro means that nobody could ever reproduce the bug. Programmers often use this when the bug report is missing the repro steps.
-
-
09 Jan 13
-
31 Dec 12
-
Keeping a database of bugs is one of the hallmarks of a good software team.
-
One of the biggest incorrect facts that programmers consistently seem to believe is that they can remember all their bugs or keep them on post-it notes.
-
n a good bug tracking system it gets automatically assigned to the lead developer for that project. And therein lies the second concept: every bug needs to be assigned to exactly one person at all times, until it is closed.
-
A bug is like a hot potato: when it's assigned to you, you are responsible to resolve it, somehow, or assign it to someone else.
-
hen a bug is resolved, it gets assigned back to the person who opened it. This is a crucial point. It does not go away just because a programmer thinks it should. The golden rule is that only the person who opened the bug can close the bug.
-
t to actually close the bug and get it off the books, the original person who opened it needs to confirm that it was actually fixed or agree that it shouldn't be fixed for some reason.
-
-
06 Dec 12
-
06 Nov 12
-
30 Sep 12
-
07 Aug 12
-
19 Apr 12
-
26 Oct 11
-
24 Jun 11
-
31 May 11
-
18 Mar 11
-
26 Feb 11
-
23 Feb 11
-
09 Feb 11
tomy smileyPainless bug tracking system
programming development testing management software bugtrack bugtracking
-
10 Dec 10
-
18 Nov 10
-
07 Nov 10
-
29 Jun 10
-
20 May 10
Juha KrapinojaTop Ten Tips for Bug Tracking
bugtracking programming development software tracking management testing bug howto
-
06 Apr 10
seppkurtEvery good bug report needs exactly three things.
1. Steps to reproduce,
2. What you expected to see, and
3. What you saw instead.bugtracking programming development software mustread tricks tips tutorial howto for:Adrian_CG for:GooVee for:SpuckyDasLama
-
11 Feb 10
-
27 Jan 10
-
08 Oct 09
-
21 Sep 09
-
11 Jun 09
-
01 Mar 09
-
18 Feb 09
-
27 Jan 09
-
25 Jan 09
-
06 Jun 08
-
01 Apr 08
-
03 Feb 08
-
12 Jan 08
-
- Steps to reproduce,
- What you expected to see, and
- What you saw instead.
Every good bug report needs exactly three things.
-
- A good tester will always try to reduce the repro steps to the minimal steps to reproduce; this is extremely helpful for the programmer who has to find the bug.
- Remember that the only person who can close a bug is the person who opened it in the first place. Anyone can resolve it, but only the person who saw the bug can really be sure that what they saw is fixed.
- There are many ways to resolve a bug. FogBUGZ allows you to resolve a bug as fixed, won't fix, postponed, not repro, duplicate, or by design.
- Not Repro means that nobody could ever reproduce the bug. Programmers often use this when the bug report is missing the repro steps.
- You'll want to keep careful track of versions. Every build of the software that you give to testers should have a build ID number so that the poor tester doesn't have to retest the bug on a version of the software where it wasn't even supposed to be fixed.
- If you're a programmer, and you're having trouble getting testers to use the bug database, just don't accept bug reports by any other method. If your testers are used to sending you email with bug reports, just bounce the emails back to them with a brief message: "please put this in the bug database. I can't keep track of emails."
- If you're a tester, and you're having trouble getting programmers to use the bug database, just don't tell them about bugs - put them in the database and let the database email them.
- If you're a programmer, and only some of your colleagues use the bug database, just start assigning them bugs in the database. Eventually they'll get the hint.
- If you're a manager, and nobody seems to be using the bug database that you installed at great expense, start assigning new features to people using bugs. A bug database is also a great "unimplemented feature" database, too.
- Avoid the temptation to add new fields to the bug database. Every month or so, somebody will come up with a great idea for a new field to put in the database. You get all kinds of clever ideas, for example, keeping track of the file where the bug was found; keeping track of what % of the time the bug is reproducible; keeping track of how many times the bug occurred; keeping track of which exact versions of which DLLs were installed on the machine where the bug happened. It's very important not to give in to these ideas. If you do, your new bug entry screen will end up with a thousand fields that you need to supply, and nobody will want to input bug reports any more. For the bug database to work, everybody needs to use it, and if entering bugs "formally" is too much work, people will go around the bug database.
Top Ten Tips for Bug Tracking
-
-
10 Jan 08
-
09 Oct 07
-
21 Sep 07
-
30 Jul 07
-
18 Jul 07
-
22 Jun 07
-
25 Apr 07
-
- Steps to reproduce,
- What you expected to see, and
- What you saw instead.
Every good bug report needs exactly three things.
-
actually close the bug and get it off the books, the original person who opened it needs to confirm that it was actually fixed or agree that it shouldn't be fixed for some reason.
-
-
23 Apr 07
-
09 Apr 07
Amy HinesKeeping a database of bugs is one of the hallmarks of a good software team.
blog development howto productivity programming reference tools
-
07 Mar 07
-
27 Sep 06
-
06 Sep 06
-
12 Mar 06
-
04 Mar 06
-
28 Feb 06
Uma ShankarKeeping a database of bugs is one of the hallmarks of a good software team. I never cease to be amazed at how few teams are actually doing this. One of the biggest incorrect facts that programmers consistently seem to believe is that they can remember all
development programming software tips management bugtracking bugs
-
03 Jan 06
-
19 Oct 05
-
07 Aug 05
-
16 Jun 05
-
05 Apr 05
-
14 Feb 05
-
08 Nov 04
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.