If a bug is found at the time of release.what you do?
Answers were Sorted based on User's Feedback
Answer / ram
Meeting the deadlines and releasing the product is very
important. One has to take a call on the bug, based on the
severity.
If it is a show-stopper bug, it needs to be fixed at any
cost, otherwise the bug is medium or less than that a patch
of fixes can be provided after the release.
But the most important thing is to mention that in know
issues in the release notes.
Is This Answer Correct ? | 8 Yes | 0 No |
Answer / pnb
We do analyze the impact of the defect. The defect is
logged in the defect Tracking System.
Include the same in the agenda of Release Management
meeting. Take a "go" / "nogo" decision with all the
relevant stakeholders in loop, (Project Manager, Product
Manager, Customer etc..)
In Case of "Go" decision the defect is recorded under Known
Issue List of the Release Note and the Product /
Application is released.
In Case a no go decision the release quest is turned back
with a note on the defect identified, and MOM on No Go
decision.
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sivaprasad, global e-softsys p
Meeting the deadlines and releasing the product is very
important.
Along the product we will release notes, nothing but a
document explains about the product and list of known
issues. issues.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / srinivas rao kukalakuntla
It depends on the severity of the bug
It's like show stooper we have to sole it and release by
intemating to clients
If it is low are medium by intemating to clint we can
release by showing the around the neck
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / vivek.ranganathan
Depending upon the severity of bug ,
if it is low i will release it as alpha version
if it is high i will ask the client some time
Is This Answer Correct ? | 1 Yes | 4 No |
Can you perform regression testing performed manually?
Can any one tell me abt. QA & QC
How do you perform integration testing?
what approach do you folllow in writing test cases?
What are the different verification techniques you know?
How do you convert uses cases into test cases?
'configuration related errors' in testing means what?
can u explain what is concurrancy in testing
What is maturity level?
What are the tables in testplans and testcases?
what is the difference between product and process based projects?
what is Desk Checking?