Gv example of a defect with high priority and low severity?
Gv example of a defect with high severity and low priority?
Answers were Sorted based on User's Feedback
Answer / amulyaranjan
1.High Severity And Low Priority----If there is an application , if that application crashes after mulple use of any functionality (exa--save Button use 200 times then that application will crash)
Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days.
2.High Priority And Low Severity---- If any Web site say "Yahoo" now if the logo of site "Yahoo" spell s "Yho" ----Than Priority is high but severity is low.
Because it effect the name of site so important to do quick ---Priority
but it is not going to crash because of spell chage so severity low.
| Is This Answer Correct ? | 18 Yes | 3 No |
Answer / kumar
1. high priority and low severity :
A web site link with a spelling mistake in the companies
name.
EX - www.citybank.com
As there is no functional impact with the issue , so the
severity should be low .But the issue with spelling mistake
may block many people from navigating to the correct website
, So the issue holds a highest priority.
2. high severity and low priority.
For a link ( functionality tab) within a web site , whose
functionality is not to be released in current release plan
, if it is broken ( not working ). The defect that should
raised for this issue , should have high severity ( as the
functionality is blocked ) and low priority (as it's not
currently required ) .
NB : Feel free to shout out in case of disagreement .
| Is This Answer Correct ? | 1 Yes | 0 No |
what is test design techniques ?
What is the test harness?
what is the difference in smoke and sanity testing.?
Name three reasons why the tester may choose to record in Context Sensitive mode.
Smoke Testing is responsibility of Tester & Developer ?
name poneno dept sun 9894433467 computer This is the xls sheet a programs written to transfer this data into database write test cases and test scenario?
What is the difference between action & script ?
can anyone please tell how a rally tool is used in testing. what are the tester roles in using this tool and the detail working of this tool.
do a new defect is required to log for slight variation in steps on defect retest or the defect can be re open
Is it necessary to do regression testing after retesting
I have 2 questions: 1) What are Technical test cases 2) What are Business test case (Or Business driven test cases)
difference between regression testing and re testing?