A tester reports a software bug/defect inward the application he is testing. He feels that this is a genuine defect that needs attention. But to his stupor as well as astonishment he finds out that his põrnikas is rejected past times the developer squad amongst an excuse of “the-application-works-as-designed”! This tin plow over amongst whatever tester at some indicate inward his testing career. And this tin survive quite frustrating too; specially if the tester feels that the software defect is a serious i as well as has got potential to campaign severe impairment to the client/end user if the software is shipped amongst the defect.
Having said that, non every defect that is rejected is worth fighting for. So every bit the outset footstep of self-assessment, a tester mightiness become dorsum to the defect report that he had submitted to the programmers as well as verify if the defect written report was good defined! Few things worth verifying inward the submitted defect written report are:
a) If the defect written report had a well-written summary business as well as the steps mentioned were readable (clear as well as precise). Use of words mightiness play a vital role inward deciding the fate of a defect report. H5N1 unmarried ambiguous word mightiness suppress the seriousness of the defect as well as your defect written report could aspect similar a bunch of garbage, wasting the bandwidth of the defect tracking system!
b) If the defect written report contained whatever unnecessary step(s), adding to the confusion.
c) If the written report clearly mentioned what genuinely happened as well as what y'all expected to happen.
d) If y'all had mentioned the consequences of the defect, inward illustration it is allowed to sideslip through the Release Phase.
e) If your tone of vocalization sounded sarcastic, threatening or careless inward the defect report. Was it inward a way, capable of making the programmer confused, unreceptive, or angry?
A well-written defect written report tin differentiate a best-selling bug from a flop show! If y'all had missed to written report the defect properly, y'all should non blame the programmer for turning downwards your defect every bit “rejected”! May survive y'all should pass some fourth dimension on your bug/defect reporting skills as well as assay i time again. But suppose, y'all had reported the defect quite neatly as well as withal it was rejected, produce upwardly one's heed if y'all would pick out to become amongst the determination or rather appeal against it every bit y'all withal strongly experience that this is a serious defect that needs immediate attention. In case, y'all are planning to appeal against the rejection these are few things that y'all mightiness see doing inward companionship to increase your run a jeopardy of success:
1) Patch the holes - Look for loopholes inward your master defect written report that could survive supported amongst farther investigative information to strengthen your case. When y'all are going for an appeal, y'all should anticipate attacks on the weaker areas of your master report. You should sympathise that your written report was weak as well as unpersuasive at the outset place. So assay as well as get together every bit mush information to become far appealing this fourth dimension around.
2) Follow it up - Do some additional follow upwardly testing but about the master defect inward an endeavor to notice to a greater extent than serious consequences. If y'all are able to notice to a greater extent than areas that are affected past times the defect as well as to a greater extent than severe consequences, it should add together to your confidence level. H5N1 defect that infests a wider make of functionalities as well as has severe consequences has to a greater extent than run a jeopardy of getting attention.
3) Follow the Money - There is a pop doctrine inward criminal investigation; “in nearly of the offense cases, if y'all volition follow the coin y'all should presently able to attain the criminal”! Same tin survive applied inward testing too, acre appealing against rejection of a defect. Talk to the major stakeholders similar the Managers, the Client, Sales region staffs, Technical Support team, as well as fifty-fifty the Technical Writers. Try to notice out who volition survive nearly affected if the Product is shipped along amongst the defect. Try to larn an thought of the fiscal loss that tin resultant due to this defect if left unfixed. As James Bach defines – “A bug/defect is something that bugs individual who matters”! Try to position the “someone” for whom your defect genuinely matters as well as notice out how costly it matters.
4) Build a Scenario to back upwardly your Testing – It’s fourth dimension for story telling. This is where a tester’s story telling capability comes inward handy. Use your imagination as well as your inventiveness to weave but about a realistic story that sounds appealing as well as at the same fourth dimension is capable of conveying the seriousness of the rejected defect. Build some scenarios that exemplify how a real-time user mightiness come upwardly across the defect as well as how it mightiness impact the user inward a severe way.
5) Look out for similar defects inward Competitors - Take wages of the immense noesis base of operations of the Internet to notice out some illustration where i of your competitors had released their Product amongst a defect similar to yours as well as had to human face upwardly terrible consequences. Check inward the recent press releases, forum discussions, tidings reports, courtroom cases for a similar illustration where a defect (similar to yours) had caused serious loss (financial loss inward damage of loss inward revenue, loss inward credibility, loss inward loyal customers etc) to a competitor. If y'all already lead maintain notes of of import events related to testing, also aspect into your moleskine notebook for whatever similar incident that y'all mightiness lead maintain recorded inward there! If y'all are lucky plenty to notice such a case, your appeal should audio lot ameliorate inward the review meeting!
With proper planning, y'all tin increase the run a jeopardy of the revival of your rejected defect inward the review meeting. Do your homework good as well as produce your illustration to a greater extent than effectively. But at whatever cost, never appeal for a defect that y'all yourself are non convinced with! If your farther investigation reveals that this defect is non worth fighting for as well as has less run a jeopardy of affecting an terminate user inward existent life scenario, ameliorate y'all should mean value twice earlier going for an appeal. Fighting for a defect that is non appealing to you, mightiness resultant inward waste materials of fourth dimension as well as loss of your credibility every bit a software tester! Any thoughts?
Happy Testing…
More interesting articles here :Tutorial Software Sumber : http://www.softwaretestingtricks.com/