Eg> if an application launches perfectly 100 times but
after that it gets blocked. In this case the severity will
be high and priority will be low, as it's not affecting the
functionality of an application.
For example assume that the length of the USERNAME and
PASSWORD in the login screen is 30 (max) while testing
you came to know that it gives server error if you give
UESERNAME and Password above 25 character.
So this will be the bug with High Priority Becoz it is
displaying server error but in real time nobody is going
to give USERNAME and PASSWORD that much long so this problem
can be handled later so low severity.
Correct me if i am wrong
Vinodh Anandhan
Software Tester
9944114400
Exceed Technologies (P) Ltd
vinodh.anandhan@exceedintl.com
Chennai
Hi,
ex: If a client having some particular logo on the home
page,if that logo is missing then the bug status is high
priority and low seveority.
Because of this bug the functionality is not stopping in
the application.
But as per client it is very important.
So the status will be high priority & low seveority.
A simple and steady example is login screen.
Suppose there are only two lebels "UserId" and "PassWd"
field.
In place of "UserId" text by mistake it is "UseQ". And all
other functionalities are working fine.
This is a low severirt and high priority defect.
Simple Example
For The Allinteview.com site in the top left of the site it
is displaying site name AllInterview.com instead of this
some spell mistake is there for eg: AliInterview.com it
will be considered as High priority with low Severity bug.
The solution for this bug is very simple for the Developers
an it is not effecting any modules in the site that
indicate Low Severity.
If I am wrong plz mail me
Test cases for google home page, yahoo signin page,
elavator, traffic signals. And can anybody post the some
other testcase(on like pen,keyboard....) as interview point
of view.
along with your userid / name. ThanQ
Site Map
