1. High Severity -Low priority
Supposing, you try the wildest or the weirdest of operations in a software (say, to be released the next day) which a normal user would not do and supposing this renders a run -time error in the application,
the severity would be high.The priority would be low as the operations or the steps which rendered this error by most chances will not be done by a user.
2. Low Severity -High priority
An example would be- you find a spelling mistake in the name of the website which you are testing.
Say, the name is supposed to be Google and its spelled there as 'Gaogle'.Though, it doesnt affect the basic functionality of the software,it needs to be corrected before the release.
Hence, the priority is high.
3. High severity--- High Priority
A bug which is a show stopper.i.e, a bug due to which we are unable to proceed our testing.
An example would be a run time error during the normal operation of the software,
which would cause the application to quit abruptly.
4. Low severity --- low priority
Cosmetic bugs
(1) High Priority and Low Severity
If a company logo is not properly displayed on their website.
(2) High Priority and High Severity
Suppose you are doing online shopping and filled payment informations, but after submitting the form, you get a message like "Order has been cancelled."
(3) Low Priority and High Severity
If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
(4) Low Priority and Low Severity
There is a mistake like "You have registered success" instead of successfully, success is written.
No comments:
Post a Comment