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.

On which basis u'll prepare the test cases.

6 Answers   Semantic Space,

What agile testing? how it is process?

5 Answers  

Which are the standards for software test plans?

0 Answers  

WHAT IS PROTOCAL TESTING..EXPLAIN? L2, L3 PROTOCALS TESTING MEANS WHAT?EXPLAIN BRIEFLY

0 Answers   Wipro,

can you tell me scenarios for login page?

1 Answers   HCL,

how The engineer communicates wiht T.L as well as test manager, In wich situation this type of i mean serious commnication takes place(give me one real time example).and how the interaction will takes place between tester and client can anybody plz clatify me.

2 Answers   Accenture,

what is difference between severity and priority

8 Answers   CSC, Wipro,

What does 100% statement coverage mean?

0 Answers   3i Infotech, Infosys,

What is the difference between qc and qa? What are the responsibilities of qc and qa?

3 Answers  

What is the difference between Product-based company and Projects-based company?

22 Answers   CTS, Google, Wipro,

how will you prioritize the work?

1 Answers  

What is Catapult Testing in E-Learning Domain?

0 Answers   Raytheon,