The primary piece of work of software attempt engineer is to attempt the software as well as uncovering equally many equally possible bugs inwards software. If yous don’t know what is põrnikas as well as thus yous should outset read this article what is Bug?
Tester writes the attempt cases based on requirement as well as he execute the attempt cases on the software. Below is the picture of demo attempt case. if the expected termination is unlike than actual termination that’s hateful functionality is non working correctly.
(test cases may contains many other parameters apart from this at that topographic point are pre-requisite, attempt data, attempt pace as well as remark etc.)
So to teach this functionality fixed tester ask to tell this põrnikas ,defect to the developer thus developer tin create it, tester has to tell this inwards exceptional nether what scenario or nether which province of affairs software behaves unexpected. Tester can’t teach to the developer as well as says that hello this is non working properly, teach this fixed for me. This is non proper way, as well as thus what is the proper way to written report the bug? Proper way is to write the exceptional written report nearly bug.
We Tester’s ask to write exceptional description which should incorporate needed information, using this information developer should locomote able to simulate the bug. So how are nosotros going to hit that? Either nosotros tin job defect management tools similar BugZila , BugNetetc. or job tin also job Word or Excel file. This depends on the scheme how are they reporting their bug, most of the companies all the same prefer to job give-and-take or excel file.
I am going to explicate how to written report a põrnikas inwards Word File.Word file should incorporate next fields for effecting põrnikas reporting. You volition uncovering these fields across all the defect management tools.
- Bug ID : it is a unique id that nosotros ask to hand to each bug. Giving the unlike ids to põrnikas help to identifying as well as tracking the bug. For representative if yous conduct keep establish põrnikas related to User interface yous may write it equally UI_1 as well as for whatever functional põrnikas FN_1. You tin write it alongside to a greater extent than details similar Login_UI_1 agency yous conduct keep establish UI põrnikas inwards login module.
- Project Name : Software mention on which nosotros conduct keep establish that bug. There mightiness locomote a province of affairs inwards which yous conduct keep allotted multiple testing projection at the same time. So this volition help yous as well as other squad members to know, this põrnikas related to which project.
- Module Name : Software is made of many module, nosotros ask to specify inwards which module nosotros conduct keep establish the bug. For representative an institutional software volition conduct keep Registration module, receipt module, online attempt module, library module etc. as well as suppose nosotros establish the põrnikas inwards online attempt module as well as thus nosotros ask to write online attempt module.
- Level or Phase : There are iv grade of testing as well as those are Unit testing, Integration testing, System testing as well as UAT. Here nosotros ask to specify when defect is found.
- Defect Type : hither nosotros ask to specify the type of defect.Means whether that põrnikas is related to functional bug, non-functional põrnikas or whatever necessary enhancement. If whatever module is difficult to sympathize they tester may hand simply about suggestions to brand that module user friendly.
- Severity : Severity tell the bear upon of exceptional põrnikas on the software. We ask to define the bugs severity equally High, medium as well as low. Severity volition locomote high if nosotros conduct keep establish a põrnikas as well as because of that põrnikas nosotros can’t croak on our testing further. E.g. login functionality of Facebook is non working this põrnikas volition marked equally severity High. Low Severity bugs are those bugs similar spelling error inwards text incorporate or at that topographic point is a incorrect icon to whatever button.
- Priority : Priority is related to the time.Means urgency of fixing the põrnikas as well as nosotros also define the priority of the põrnikas equally High, medium as well as low. If the severity of the põrnikas is high as well as nosotros can’t croak on our testing without fixing this põrnikas as well as thus the priority of that põrnikas would locomote grade equally High. And inwards incremental as well as iterative type software evolution wheel the requirements are divided into pocket-size builds, if nosotros conduct keep establish a põrnikas inwards module which is included electrical flow create unloose as well as thus that põrnikas is marked equally High as well as suppose nosotros conduct keep establish the põrnikas is a module which is non the component division electrical flow create unloose as well as thus that is marked equally Low priority.
- Summary : Summary agency 1 describe of piece of work disputation that gives basic sentiment of the defect. Like login functionality is non working fine, registration page is non opening etc. it is non an details description simply 1 describe of piece of work statements.
- Description : In this plain nosotros ask to hand a exceptional explanation nearly the defect. We ask to hand pace past times pace procedure to reproduce the põrnikas as well as if ask nosotros tin add together screenshot. Developer should easily sympathize what the põrnikas is as well as how to reproduce it.
- Status: this is the final field, hither nosotros ask to write the condition of the bug. Bug goes through unlike status. Like when tester finds a põrnikas as well as thus that bug’s condition is new. When assigned to developer as well as thus its condition volition locomote assigned. Other condition are Duplicate, Deferred, Fixed, Closed etc. You volition teach detailed noesis nearly this condition inwards Defect life cycle.
Incident written report inwards give-and-take file is looks similar equally shown above.