suppose a tester has critical bugs and according to schedule product to be release in next week. in that scenario what should be done.
I follow the below way
1)interact with the developer how much time is needed to fix those critical bugs . then i discuss the same with my team lead and qa manager . we shall have a team meeting with developers qa manger and qa lead to discuss about the issue. then qa manager is goign to interact with the client and postpone the release so taht teh product is relased bug free.
I WOULD APPERICATE GUYS CORREDT ME IDF IAM WRONG. PLEASE TELL ME ABOUT ALTERNATIVES SCENARIO
How about you simply report the bug with a formal set of documentation about the impact and urgency and leave it up to management to decide if it can be shipped or not? Your job is to test software, to see if there are any more bugs where that one came from. If you spend your time doing the job of the manager you cannot spend enough time doing the testing job, that leaves other potential bugs unreported, and unfixed, and that will reflect on you. Sure, you went all out over one bug, but you didn't find the 99 other bugs the clients report.
Thanks Frut Bos for spending your valuable time.
how about test lead ? how he will be reacting to this issue.. What is the process the industry will be following is such scenario?
I think risk analysis should be done to find out the root cause of the issue... Any more scenarios.....
Satish - to answer your question about what the "process the industry" is, there is no "industry standard" practice. The practice is what your company sets up in it's procedures. For some, it may be a test lead function to do risk analysis and classify defects. In other companies, that is the role of the project manager. In yet others, that is the role of an oversight committee. It all depends on what your company has set up and what your people are comfortable with. The roles may even change project to project in the same company.
Frits explained it just right - about the only "universal" concepts that can be brought out is that someone in a management position makes the call about the severity and priority of a defect and how to deal with it. The tester uncovers the bug and takes further action as directed by his or her management.
What usually happens here is that, We report the bug, with a appropriate severity level and then Meet/send a mail to the SQA Project/Team lead explaining the bug and its possible effects on the system.( Remember, that most bug tracking systems automatically send mails, but since it may be a little slow in its cycle, we send a mail individually).Once we've done that, we Continue testing as usual. We Give suggestions on how to go from there only when asked, or only if we have a good rapport with the SQA leads.
What I would do in your scenario is report the defect in the regular format and as SureshJ mentioned also send out an email (if the defect tracking tool doesn't already do that).
Bottom line is that you need to let the project manager and the business representative know about the critical defect. They are the ones who will make the decision whether to release the application with the critical bug or delay the release so that it can be fixed. I don't think either the QA team lead or manager can do much apart from what is mentioned above unless they are a part of the approval board which makes the Go/No-Go decision.