Is it worth your time? Why does this happen all the time? What can be done to get it fixed?
Every tester faces this situation and nearly everyone falls for the standard solution: report, forget and do not expect much. Developers are really slow on fixing bugs as it takes a lot of efforts and working hours, prolonging the estimated development and testing term, which is highly undesirable.
Why should a tester report bugs then?
Do you need doing a job that is not giving results? Our answer is: Yes… and No.
The main flaw of bug reports is nearly always the same: testers give brief explanations of a single bug in their report, forcing stakeholders to do a big amount of job finding the possible reasons of bug existence and ways of its solution.
To say even more, it is sometimes easier to build another solution, than fixing this bug. If it does not force the app to crash, it can be surpassed. This actually shows the sphere of stakeholders’ interests: they need a working app as fast as possible and fixing bugs is not going to speed up the process; developing alternate solutions might be – and usually is- faster and easier.
The main result is approximately 1 of 10 bugs is fixed. It sometimes gets really frustrating. Is it worth your time and efforts? As long as you are paid for the job, you might say.
There are several solutions for this case we want to offer you:
- Creating clear and understandable reports. Tester usually knows the code nearly as good as the developer and skilled tester might see the solution at once. Showing your stakeholders’ you value their time and efforts by offering the possible bug origin and ways for solution is awesome. This way you might expect 4 or even 5 of each 10 found bugs to be fixed.
- Creating 1 mega-report instead of several standard ones. Following the first advice is also a must. When your developers see the big volume of data you prepared collected altogether – it seems the app will never work without fixing all of the bugs.
- Offering your situation vision and possible ways of solution (if any). The more experienced the tester becomes, the easier finding bug fixing solutions becomes for him.
Let us form a conclusion
- All of the bugs you encounter must be reported.
- The more clear and specific your report is, the better. Even if not all of the bugs are fixed at once, having that report on file could help a lot later.
Do your best and your efforts will be rewarded!