Answer / maninder

Crash of Application after 99 times clicking on OK button
Severity :- High as it is a Crash
Priority :- Low as rarely used scenario

Answer / rajesh.v

*Priority means “Importance of the defect w.r.t customer
requirement.
*Severity means “seriousness of the defect w.r.t functionality.

HpLs:
Error in user (Spelling mistake, error message not clear)

HpHs:
Data enter to front end of an application is not getting
stored in the database.

LpHs:
Client requirement is 500 records have to be stored in
database, but the database is designed such that it can be
handled up to 700 records. When we enter the records into
the data base it is storing only 600 records.

LsLp:
Font size filed level validations tab order.

Answer / rajeshwar rao

In any application the application will be crashed the
multiple use of any fucnality.for ex save button use 200
times. The application will be crashed. So high severity.
but low priority. Because there is need to debug the right
now u can debug it after some days

Answer / zahid

High Priority low seviority: High priority example is
suppose the company logo name is wrong or spelling mistake
in title.Here due to this the application is not going to
crash so the seviority is low, but it has a great impact so
the prority is high.

Low priority High Seviority: Suppose on clikc of submit
buttom 200th times the application is getting crashed. here
the priority will be high bcoz the application is getting
cashed, but its not going to effect much so the priority is low.

Answer / shwetha

severity means seriousness of defect w.r.t functionality
priority means importance of the defect w.r.t customer
requirements


HSLP:
if the customer expected a table is to store 100 records .
the table is designed for 500 records while entering sample
data it taking or storing only 200 records so it is high
severity and low priority (customer require only 100
records so it is low priority)

Answer / sujan reddy

I have modules like I)Accounts II)Reports
Requirement:
The Account details which were entered in the Accounts
module should be reflected in the reports module.
High severity:the accounts information which were entered
in the accounts module is showing right values in the
accounts module but those values are not reflected in the
Reports module.its a high severity and high priority bug
but in some situations that Reports module is not fully
implemented and that was in the development stage than it
will be considered as high severity and low priority bug.

Answer / selva ganapathi

Consider the scenario where migration from one old card
payment system to a new card payment system.

During the testing we have to check whether all the valid
cards accepted by that firm should be working as expected,
that means the payment system should give a succesful
authorization response for all valid card type (Master,
visa,maestro etc...) accepted by the store.

But if the system works fine for 80 percentage of the card
types, agreed by the company and does not give a successful
response for remaining 20 percentage of card types of all
valid cards.

This issue can be categorized as low severity, as test team
can show progress and test the new functionality with the
accepted valid card types.
But the issue needs to be fixed immediately as it going to
affect the business in various ways like

* Customer dis-satisfaction if he has valid card
* Revenue loss.
* loosing the valid customer base
* Lose of value and reputation of the store.

Hence this issue is comes under high priority and low
severity case.

Answer / sahaya

Priority-deals with the Urgency of the fix to be provided-should be Urgent/High/meidum/low

Seveority-should be determined based on the impact of the defect(high/medium/low) in the functionalities/application

Answer / selvagnapathi

High severity and Low priority:

Consider a card payment system which would be designed to
gives responses like

Accept
Decline
Refer

while swiping the cards.

On using valid cards all the functionalities are working as
expected except the REFER.

In this case testing cannot be in progress for the test
case related to REfer. Hence the severity for this defect
should be High as Refer functionality is not working.

But priority would be low(P3) as other functionalities like
Accept and decline are wroking and end to end payment
functionalities from business perspective could be tested
using the Accept Response.Hence development team can take
some time to give a solution for this issue

Hence defect related to this type could be categorized as
Low priority and high severity.

Answer / manisha

High Severity and low priority : Batch feeds of any
perticular events are generated at last day of every month.
but in any month feed has not been generated . which
ditrectly effects the business but on functionality of
code. beaucse of having minor effect on SOAP or CFT flow.
it happens not frequently

Could Login Id field accept special characters?

3 Answers  

write testcases for open dialogbox

0 Answers  

How will you do beta testing?

0 Answers   Aricent,

What are the bugs we cannot find in black box?

0 Answers  

how you r executing Test case explain in detail

2 Answers  

what is the diff between ad hoc and exploratory testing ?

5 Answers   Synergy,

How to test a Falsh player scrollings?

0 Answers   Accenture,

You have been given 2 projects to test, what are the key factors you consider when prioritizing you work load?

1 Answers   Syncada,

what is mean by client and server?

5 Answers  

What is Difference between White-box Testing and Unit testing?

6 Answers   AZTEC, College School Exams Tests,

Do we have to execute all the test cases while doing sanity testing and regression testing??(manual testing)

2 Answers  

how do we know our perticular task is compltely tested or not

2 Answers