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.

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 .

If PRS is given to you on say XYZ functionality then which different types of testing you will perform . Please arrange these types in sequential manner in which you will perform?

1 Answers   TCS,

---

When do you stop testing?

3 Answers   Standard Bank,

---

difference between stress testing and loadtesting

3 Answers  

---

what is your test strategy?

2 Answers   Zensar,

---

wat is ur involvement in user acceptance testing

9 Answers   Polaris,

---

What is V Model?

3 Answers  

---

What's the difference between Load and Stress testing ?

4 Answers   CTS,

---

what is tracebility matrix and what will be there in tracebility matrix?tell me details like idno, discription....etc.pls any one answer this question?

5 Answers   IBM,

---

Do you agree testing is needed?Justify it?

1 Answers  

---

*) Internal review defect gets detected… 1) During peer review. 2) By the own stuff member onsite/offshore. 3) During Informal review process. 4) None of these 5) All of these

0 Answers  

---

manual&automation testing

1 Answers   HCL,

---

This is the question related to Traceability Matrix. Say we have 10 requirements for a project. If one of the testing team member misses the 9th requirement. Then how can we justify the Traceability Matrix and what is the further action to be taken. Please advice.

6 Answers   ACS,

---