True Story of Braidy:
Braidy once got oppurtunity to work as a tester in a software company. As usual the company lacked testing culture.
The bugs reported by QA/testing team were not always reviewed and all the bugs were not always fixed. Most of the times, the focus was on fixing the blocker and major issues only. Despite the fact that Braidy and his team was working hard, the information provided by testing was always ignored. Their managers hardly believe what testers uncovered. They used to say “Let Client report the bug then we will fix this..”. Management team always had predetermined plans/dates for software delivery. Braidy was not happy with all this.
Days passed, software was delivered to client. UAT happened and client accepted the software. After few weeks, client started reporting issues. Every week client was reporting 2-3 bugs. Both client and Senior management of software company were not happy.
Bugs were communicated to testing and dev teams. Management team started questioning the Development and Test leads via emails. Braidy checked the bug tracker and found that almost all the bugs were already reported by testing team during the testing cycles but these bugs were not fixed and were in open/new stage. Braidy replied to one of the email and asked Project Manager/Delivery manager “Why these bugs were ignored and not fixed? Now these bugs become high priority and critical for client?”
No one from the management team replied to Braidy’s email. But he observed some changes – After each test cycle, the bugs were reviewed, managers started analysis/review of the test reports/results and started getting inputs from test teams.
Moral of the story –
1. When I hear “It’s better for you, Customer, to report that than me,” I detect an organization that listens to neither customers nor workers ~Michael Bolton
2. If you aren’t going to believe what the testers uncover, either you have the wrong people or you need to get serious about helping them build their credibility. Testing is never just a matter of hiring and hoping.
~Gerald M. Weinberg – Book “Perfect Software and other illusions in Software Testing.
3. If you’re going to ignore information or go ahead with predetermined plans despite what the tests turn up, don’t bother testing. (Actually, it can’t really be considered information if you don’t use it.)
~Gerald M. Weinberg – Book “Perfect Software and other illusions in Software Testing.
4. Only Testing team is not responsible for Quality.
As a Tester we have to consider the project as the owner and user of that particular requirement.
“Heya i am for the initial time here. I discovered this board and I to find It really useful & it aided me out much. I’m hoping to present a thing once again and help others like you served me.”