Painless bug tracking

Found an article titled "Painless bug tracking" and decided to read it onky because of the word 'painless'. By, promotional article for their bug tracking software, called FogBUGZ. The article was really good and i liked it. It is so similar to our company when i was working. It is really neccessary to have a bug tracking software. although a simple database did not help to us, there was no point to have registered all the bugs. it was more important to have database with a functionality of task assigment among developpers, consultants, testers. It was important and we wanted to make sure that every person, working directly with users and hearing about the problems - that thy should wrote down all of them. that is why the programmers, and we testers did not use to accept the requests to fix the bug when it was not in the database. Usually a person would come, say something and go away, after a week he inquires about the problem fixing, but they all remain in the air - there were so many things to do and to test that usually we forget.... it is also important for the developper to see how much work he has, how many bugs he has assigned. our company made a software for inner needs - task assigment among all workers.
the next thing i liked in the article - Top Ten Tips for Bug Tracking. especially these: 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.

there was an interesting point on keeping the bug database simple - not adding additional fields to have more information on it. i remember we would always think about adding something more... and then the consultants say it is tooooo complicated to fill the form...


Popular posts from this blog

tester's day!

Security testing

Retrofitting testing - what is it?