Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / santhosh k
Bug status description:
These are various stages of bug life cycle. The status
caption may vary depending on the bug tracking system you
are using.
1) New: When QA files new bug.
2) Deferred: If the bug is not related to current build or
can not be fixed in this release or bug is not important to
fix immediately then the project manager can set the bug
status as deferred.
3) Assigned: ‘Assigned to’ field is set by project lead or
manager and assigns bug to developer.
4) Resolved/Fixed: When developer makes necessary code
changes and verifies the changes then he/she can make bug
status as ‘Fixed’ and the bug is passed to testing team.
5) Could not reproduce: If developer is not able to
reproduce the bug by the steps given in bug report by QA
then developer can mark the bug as ‘CNR’. QA needs action to
check if bug is reproduced and can assign to developer with
detailed reproducing steps.
6) Need more information: If developer is not clear about
the bug reproduce steps provided by QA to reproduce the bug,
then he/she can mark it as “Need more information’. In this
case QA needs to add detailed reproducing steps and assign
bug back to dev for fix.
7) Reopen: If QA is not satisfy with the fix and if bug is
still reproducible even after fix then QA can mark it as
‘Reopen’ so that developer can take appropriate action.
8 ) Closed: If bug is verified by the QA team and if the fix
is ok and problem is solved then QA can mark bug as ‘Closed’.
9) Rejected/Invalid: Some times developer or team lead can
mark the bug as Rejected or invalid if the system is working
according to specifications and bug is just due to some
misinterpretation.
| Is This Answer Correct ? | 13 Yes | 4 No |
Post New Answer View All Answers
A type of functional testing, which investigates the functions relating to the detection of threats, such as virus from malicious outsiders?
What is equivalence class?
Which one of the following activities is the most efficient and most cost effective at identifying defects? 1. Prototyping 2. Unit test 3. Beta test 4. Design/code inspection 5. Risk analysis
Explain storage testing?
What is a user manual?
Explain acceptance testing?
Explain the tasks involved in planning and control.
What is random/monkey testing?
What is qa engineer?
What is the one key reason why developers have difficulty testing their own work?
I. Requirements are formally reviewed. II. Requirements are formally approved. III. Requirements are placed under configuration control. IV. Requirements are implemented in code. Using the above statements, when are requirements considered baselined? 1. I and II 2. I, II, and III 3. I, II, III, and IV 4. I only 5. I, III, and IV
Explain testing?
What is the most critical component in SAN?
What are the experience-based testing techniques?
waht are somking types
