When I fill my resume, when I look at other tester's resume, I find people mention bug reporting and tracking as a responsibility. But being a tester is it enough?
I hear many testers stating that their job description involves only bug reporting. Why should they bother if its fixed? If it is fixed, then they verify and do regression. If not, then why bother, its lesser work. Others team mates encourage this attitude as it helps reduce their workload: Developers are always busy and can do without solving another bug, Managers have to manage critical deployments and can do without extra work on developers.
We took an initiative from our end as the testing team. After every bug tracking, we used meet our manager and discuss/debate with our list of bugs which had to be fixed before next deployment. This effort was done in addition to the fact that the manager had himself prioritized some bugs. Initially we were not welcomed, but after few cycles of deployment, our team mates understood the value of our effort: At the end, aim was to make software quality better with every deployment. As time went on, due to our continued effort, we got positive feedback for a high quality software from our customer base. Although it was a team effort, we testers were especially praised for our extra efforts.
I hear many testers stating that their job description involves only bug reporting. Why should they bother if its fixed? If it is fixed, then they verify and do regression. If not, then why bother, its lesser work. Others team mates encourage this attitude as it helps reduce their workload: Developers are always busy and can do without solving another bug, Managers have to manage critical deployments and can do without extra work on developers.
We took an initiative from our end as the testing team. After every bug tracking, we used meet our manager and discuss/debate with our list of bugs which had to be fixed before next deployment. This effort was done in addition to the fact that the manager had himself prioritized some bugs. Initially we were not welcomed, but after few cycles of deployment, our team mates understood the value of our effort: At the end, aim was to make software quality better with every deployment. As time went on, due to our continued effort, we got positive feedback for a high quality software from our customer base. Although it was a team effort, we testers were especially praised for our extra efforts.
Posts
