Hi,
I am Anil kumar I would like to give information about software testing and quality.
Testing :-
Verify the application as per the customer requirements
Verify can we develop the right product or not
Verify the application as per industry standards
Verify the application for bug free
Combination of Verification and Validation
I am Anil kumar I would like to give information about software testing and quality.
Testing :-
Verify the application as per the customer requirements
Verify can we develop the right product or not
Verify the application as per industry standards
Verify the application for bug free
Combination of Verification and Validation
Good job...........
ReplyDeleteHi anil Sir,My name is Ramu.
ReplyDeleteCan u explain the Priority and severity with good example.I hope You can give with good example.
Difference between Severity and Priority of a defect has been the most common question for Software Testing job interviews. This is one topic; even very senior managers have conflicting views sometimes.
DeleteDefect Severity
Defect Severity signifies degree of impact the defect has on the development or operation of a component application being tested. It is the extent to which the defect can affect the software. The severity type is defined by the Software Tester based on the written test cases and functionality.
Defect Severity may range from Low to Critical
Critical - this defect is causing system failure. Nothing can proceed further. It may also be called as a show stopper
Major - highly severe defect, is causing the system to collapse, however few parts of the system are still usable, and/or there are a few workarounds for using the system in the collapsed state too
Medium - is causing some undesirable behavior, however system / feature is still usable to a high degree
Low - is more of a cosmetic issue. No serious impedance to system functionality is noted
Defect Priority
Defect priority signifies the level of urgency of fixing the bug. In other words Priority means how fast/ how soon it has to be fixed. Though priority may be initially set by the Software Tester, it is usually finalized by the Project/Product Manager.
Defect Priority may range from Low to Urgent
Urgent: Must to be fixed before any other high, medium or low defect should be fixed. Must be fixed in the next build.
High: Must be fixed in any of the upcoming builds but should be included in the release.
Medium: should take precedence over low priority defects and may be fixed after the release / in the next release.
Low: Fixing can be deferred until all other priority defects are fixed. It may or may not be fixed at all.
Differences between Defect Severity and Defect Priority
Severity
Priority
Severity is associated with standards/functionality.
Priority is associated with scheduling.
Severity refers to the seriousness of the bug on the functionality of the product. Higher effect on the functionality will lead to assignment of higher severity to the bug.
Good Job.... good information thank you...
ReplyDeletethank u for u r replaying.good job it is very helpful to me@nag,Anil
ReplyDelete