Painless bug tracking

Found an article titled "Painless bug tracking" and decided to read it onky because of the word 'painless'. By joelonsoftware.com, 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...

Comments

Maid Service San Diego said…
Hi greaat reading your blog
8:12 PM
Post a Comment

Popular posts from this blog

Ieškomas testuotojas: ASW

PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTAS Aprašymas: SIŪLOMAS DARBAS PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTUI VILNIUJE ARBA KAUNE. Detali informacija: “CVO Technology Recruitment” klientas – viena didžiausių IT įmonių Lietuvoje ir kitose Baltijos šalyse. Pagrindiniai įmonės privalumai - verslo procesų išmanymas, ilgametė projektų valdymo patirtis Lietuvoje ir užsienyje bei techniniai programinės įrangos vystymo įgūdžiai. Šiuo metu įmonė plečiasi ir į komandą VILNIUJE arba KAUNE kviečia prisijungti PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTĄ (-Ę). Darbo pobūdis: Sistemų testavimas: klaidų taisymas ir tinkamas jų aplinkybių suformulavimas; Tarpinių ir galutinių testavimo rezultatų apibendrinimas; Komandos darbo koordinavimas bei konsultavimas testavimo klausimais; Srities naujienų sekimas ir pasiūlymai dėl jų diegimo. Reikalavimai kandidatui: Ne mažesnė nei 3 metų darbo patirtis
Read more

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ask for
Read more

Security testing

Image
My previous employer organised internal security training for QAs. As coming not from development background, they were good, but too tough for me. There is really good free resource on pluralsight.com by Troy Hunt " Hack yourself first ". It is declared for developers to deepen their knowledge of security. Myself I found it really cool as the author explains everything clearly with good examples.
Read more