Answer / vrushketh

First check how many test cases have been blocked by this
defect. try to get fix from developer as early as possible.
In case the devloper is not able to give fix or it i retest
failed then mention the defect in the release notes.

Regards,
Vrushketh

Answer / bhaskar

1) If the bug is critical or a show stopper inform all the stakeholders that the bug needs to be fixed before the release so that the client can push the release further if there is a possibility

2) Try to get the developer fix the bug asap if it can be fixed and tested it thoroughly

3) If the bug cannot be fixed and it has to be released to the production ,mention the bug as known issue in release notes

4) if the bug is not critical it can be deferred to next release

5) See if there is any switch in the code so that developer can switch off the particular functionality or module and release other functionalities which are not dependent

Answer / nag

If D&S will not be able to fix the defect in specified
timelines, business will ask WA or HF..if both not
possible ..then Management team will initiate CCB meeting
for all stake holders(Business, QA, D&S...) and they can
push the release until defect fix...

Answer / @mit

In this case,v verifed that how many test cases are
affected by this critical bug.Then v discuss it with
developer with same staus of bug and test case.

If they fix all bugs then v perform regression testing,if
no major bug was found then its ok otherwise v discuss the
same scenairo with PM and TL and asked to delay the release
as it contain critical bug.Or v discuss the same scenairo
with client(if have intraction wid clent).
If client or PM were ready to delay the release then its
ok otherwise we mention the same critical bug in Test
Summary Report under "Known Bug" section.

Answer / venu

1) As you mentioned its critical bug first hear v need to see the priority if it has less priority then we can deliver as it is and fix the issue in upcoming build.

2) If the priority is high then explain the situation to Clint and get some time and fix it.

3)If client is not ready to extend the release then analyse the severely of it and start workaround(Way to fix) for it and in release note mention known issue

Answer / daniel

MY answer is from the TPM or PM point of view

- Assessment the impact of this critical bug – which area/feature get affected.
- Find out any workaround in case the bug cannot be fixed
- Set a 24 hours urgent plan for fixing and testing and also getting the time for resolution/testing
- Provide recommendation for go or no go decision for final decision maker
- If go with this critical bug, release note need to cover the issue and how to recover
- If no go, the timeline for patch release.

tell me about ur current proect? how can we start, what should we explain? should we expalin the entire proj or only our module? july27 brahma412@yahoo.co.in plz help me

4 Answers  

While doing system testing your have missed out some issues. The same issue is found by customer and he reverts back to you for an explaination. How do you convince him or how do you justify yourself about your testing?

3 Answers   Broadridge, HP,

what is the difference between Risk based and Requirement based testing???

0 Answers  

How can you decide max number of testcases for a Module?

3 Answers   Verizon,

How will you give estimation when preparing Test Plan

1 Answers   Virtusa,

what is database testing

2 Answers  

What is Test methodology, Testing type , Testing approach, Testing technique & Testing methods. Explain with example.

0 Answers  

why QA team is necessary for an organization?

0 Answers  

What is bidirectional traceability?

3 Answers  

what is walkthrough?

8 Answers  

What is meant by Domain knowledge?What are the Domains?How many types of Domains are there?

6 Answers  

Differentiate Test strategy and Test case?

1 Answers