The primary piece of job of software evidence engineer is to evidence the software in addition to detect equally many equally possible bugs inward software. If yous don’t know what is põrnikas in addition to thus yous should commencement read this article what is Bug?
Tester writes the evidence cases based on requirement in addition to he execute the evidence cases on the software. Below is the picture of demo evidence case. if the expected resultant is dissimilar than actual resultant that’s hateful functionality is non working correctly.
(test cases may contains many other parameters apart from this in that place are pre-requisite, evidence data, evidence footstep in addition to remark etc.)
So to larn this functionality fixed tester take away to tell this põrnikas ,defect to the developer thus developer tin mail away cook it, tester has to tell this inward exceptional nether what scenario or nether which province of affairs software behaves unexpected. Tester can’t larn to the developer in addition to says that hi this is non working properly, larn this fixed for me. This is non proper way, in addition to thus what is the proper way to study the bug? Proper way is to write the exceptional study virtually bug.
We Tester’s take away to write exceptional description which should incorporate needed information, using this information developer should travel able to simulate the bug. So how are nosotros going to make that? Either nosotros tin mail away utilization defect administration tools similar BugZila , BugNetetc. or utilization tin mail away also utilization Word or Excel file. This depends on the arrangement how are they reporting their bug, most of the companies all the same prefer to utilization give-and-take or excel file.
I am going to explicate how to study a põrnikas inward Word File.Word file should incorporate next fields for effecting põrnikas reporting. You volition detect these fields across all the defect administration tools.
- Bug ID : it is a unique id that nosotros take away to make to each bug. Giving the dissimilar ids to põrnikas assistance to identifying in addition to tracking the bug. For representative if yous receive got establish põrnikas related to User interface yous may write it equally UI_1 in addition to for whatsoever functional põrnikas FN_1. You tin mail away write it amongst to a greater extent than details similar Login_UI_1 agency yous receive got establish UI põrnikas inward login module.
- Project Name : Software advert on which nosotros receive got establish that bug. There mightiness travel a province of affairs inward which yous receive got allotted multiple testing projection at the same time. So this volition assistance yous in addition to other squad members to know, this põrnikas related to which project.
- Module Name : Software is made of many module, nosotros take away to specify inward which module nosotros receive got establish the bug. For representative an institutional software volition receive got Registration module, receipt module, online evidence module, library module etc. in addition to suppose nosotros establish the põrnikas inward online evidence module in addition to thus nosotros take away to write online evidence module.
- Level or Phase : There are iv degree of testing in addition to those are Unit testing, Integration testing, System testing in addition to UAT. Here nosotros take away to specify when defect is found.
- Defect Type : hither nosotros take away to specify the type of defect.Means whether that põrnikas is related to functional bug, non-functional põrnikas or whatsoever necessary enhancement. If whatsoever module is difficult to sympathize they tester may make approximately suggestions to brand that module user friendly.
- Severity : Severity tell the bear upon of exceptional põrnikas on the software. We take away to define the bugs severity equally High, medium in addition to low. Severity volition travel high if nosotros receive got establish a põrnikas in addition to because of that põrnikas nosotros can’t croak along 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 fault inward text incorporate or in that place is a incorrect icon to whatsoever button.
- Priority : Priority is related to the time.Means urgency of fixing the põrnikas in addition to nosotros also define the priority of the põrnikas equally High, medium in addition to low. If the severity of the põrnikas is high in addition to nosotros can’t croak along our testing without fixing this põrnikas in addition to thus the priority of that põrnikas would travel grade equally High. And inward incremental in addition to iterative type software evolution wheel the requirements are divided into small-scale builds, if nosotros receive got establish a põrnikas inward module which is included electrical flow construct unloose in addition to thus that põrnikas is marked equally High in addition to suppose nosotros receive got establish the põrnikas is a module which is non the component subdivision electrical flow construct unloose in addition to thus that is marked equally Low priority.
- Summary : Summary agency i trace of piece of job tilt that gives basic persuasion of the defect. Like login functionality is non working fine, registration page is non opening etc. it is non an details description simply i trace of piece of job statements.
- Description : In this plain nosotros take away to make a exceptional explanation virtually the defect. We take away to make footstep yesteryear footstep procedure to reproduce the põrnikas in addition to if take away nosotros tin mail away add together screenshot. Developer should easily sympathize what the põrnikas is in addition to how to reproduce it.
- Status: this is the terminal field, hither nosotros take away to write the condition of the bug. Bug goes through dissimilar status. Like when tester finds a põrnikas in addition to thus that bug’s condition is new. When assigned to developer in addition to thus its condition volition travel assigned. Other condition are Duplicate, Deferred, Fixed, Closed etc. You volition larn detailed noesis virtually this condition inward Defect life cycle.
Incident study inward give-and-take file is looks similar equally shown above.