Q. What is a test strategy?
Answer:
A test strategy must address the risks and present a process that can reduce those
risks.
The two components of Test strategy are:
a) Test Factor: The risk of issue that needs to be addressed as a part of the test
strategy. Factors that are to be addressed in testing a specific application
system will form the test factor.
b) Test phase: The phase of the systems development life cycle in which testing
will occur.]
Q. When to stop testing?
Answer:
a) When all the requirements are adequately executed successfully through test
cases
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over]
Q. Your company is about to roll out an E-Commerce application. It is not
possible to test the application on all types of browsers on all platforms and
operating systems. What steps would you take in the testing environment to
reduce the business risks and commercial risks?
Answer:
Compatibility testing should be done on all browsers (IE, Netscape, Mozilla etc.)
across all the operating systems (win 98/2K/NT/XP/ME/Unix etc.)]
Q. What’s the difference between priority and severity?
Answer:
“Priority” is associated with scheduling, and “severity” is associated with standards.
“Priority” means something is afforded or deserves prior attention; a precedence
established by order of importance (or urgency). “Severity” is the state or quality of
being severe; severe implies adherence to rigorous standards or high principles and
often suggests harshness; severe is marked by or requires strict adherence to
rigorous standards or high principles, e.g. a severe code of behavior. The words
priority and severity do come up in bug tracking. A variety of commercial, problemtracking/
management software tools are available. These tools, with the detailed
input of software test engineers, give the team complete information so developers
can understand the bug, get an idea of its ’severity’, reproduce it and fix it. The fixes
are based on project ‘priorities’ and ’severity’ of bugs. The ’severity’ of a problem is
defined in accordance to the customer’s risk assessment and recorded in their
selected tracking tool. A buggy software can ’severely’ affect schedules, which, in
turn can lead to a reassessment and renegotiation of ‘priorities’.]
14 comments ↓
How priority and severity are determined?
Are they only decided by the tester by his own or is there any fix criteria to decide it?
I mean if i found a bug i will assign it priority what i think is relative but for the same bug other tester can assign different priority and severity … so how should one maintain this as a standard?
Q. When to stop testing?
Answer:
a) When all the requirements are adequately executed successfully through test
cases
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over
if we have multiple option question
then which of the above is most correct answer
I feel, none of above mentioned options are adequate to stop testing.
I could have been,
1. Raised defect status are of low priority having very less impace on system
2. Business agrees to stop the testing & is ready to bear all the risk
3. Atleast all the high priority requirement related test cases are covered.
give more examples for priority and severity defects
IN general the tester only assigns severity to the bug. The priority is assigned by the project manager. The priority of the bug might differ according to the release and hence the project manager will assign priority depending on how important that bug fix is for the release.
Please correct me if i am wrong.
-subha
Would like to know what is the difference between test plan and test stratergy.
severity means how serious the bug is?
pripority means a message to the developer what defect are taken first ,next and ;last for defect recttification
How to decide the priority and severity ?
your answer provide nice information ,but i have one
quiery that is
“can priority dependes on severity”?
please answer my quiery.
who decides the priority devloper or QA?
QA
Base on client requirements we decided the priority.
Means the importance of the client requirement we give the priority…
Can anyone give examples for all combinations of priority and severity like high priority and low severity,etc…
Hi all,
Can anyone tell me procedure for testing performance of web apps ?
I am single tester in my company. I want to do load /stress testing.
Please help me.
u all hvnt gve the live examples of severity and prioroty .so plkease try to gve the examples
Leave a Comment