WHAT IS BUG LIFE CYCLE YOU FOLLOW?
Answers were Sorted based on User's Feedback
Answer / sumon kashem
In my last project the bug life cycle that i followed was
new-open-assign-verify in QA-verified-staging-closed
As a QA tester whenever i find a defect i always try to reproduce it and if its a valid bug i then logged in the defect in defect section of quality center in my last project. After filling up the key elements in defect section of qc with the status of the bug New, i then send it to my QA Lead. My QA lead checks the defect and if its not a duplicated defect then he put the status open and send it to dev lead. Then dev lead assigns the defect to developer by putting the status assign. Once developer fixes the defect he then put the status verify in qa and send it back to me. Once i retest the defect by doing regression testing i then put the status of the defect verified. Then it went to staging environment and once it was cleared and valid from staging environment then my QA Lead closed the defect.
Is This Answer Correct ? | 1 Yes | 2 No |
Answer / chaitanya1987
requirements--->development--->application--->testing
if defect is found,it will set as NEW then send to
development depot
else stop testing
if developer feels that it a defect,developer will OPENS the
defect,rectifies set it as FIXED and will send it to the
testing depot
else
HOLDS or
REJECTS
if HOLDS,clarifies in meeting,
if REJECTS,
tester will either CLOSED or will REOPEN and again send
it to developer.
Is This Answer Correct ? | 1 Yes | 6 No |
when to start and stop testing?
name the types of methodologies
what is the need for different tools? why cant we manage testing with a single tool?
2 Answers Calpine Technologies,
explain the Compatibility testing
Can any one explain about state based and graph based testing? and the difference between them? Very urgent.......... Please...... Thanks in Advance......... regards, Murthy.M
Write the three important scenario or test cases for Air conditioner.
differentiate defect age build interval? what style of testing we can follow with lack of documentation?
What is difference between Development envionment and Test enviornment.
How do we use <!DOCTYPE HTML PUBLIC...> in the begining of any HTML page.
what is clinet side validation and server validation??
Which is the better way to explain tipical bug life cycle?
Generally How do we do Test Estimation. Anybody can expalin this with example. Thanks in advacne..Venkat