venkatraog

 Profile Answers by venkatraog 

• Dec 19th, 2005

 

first i understand the bug and next i report that bug to developement team through project manager.if manager also not available i am directly communicate with dev team.i am tring to convince them.

mrgreekgod

 Profile Answers by mrgreekgod Questions by mrgreekgod

• Feb 14th, 2006

 

As you said 5 bugs are high and 5 bugs are low severity.if there is no test lead or manager not available as a senior Testing Engineer i would concentrate on 5 high severity bugs.First i ll understand them and send them to the particular development team with help of project manager.If required i ll explain them the situation and about the bug severity.mean while i ll intract the client behalf of my test team and i ll make them understand the current status of the application.

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Nov 16th, 2006

 

I will tell the customer about which functionality haves the problem, and if he have time i will try to make sure that high sevierity bugs get fixed.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 26th, 2009

 

Hi

  First of all i will intimate the current status to client,  i will ask and take time for fixation and testing, if he gives time then problem was solved, if he not given the time, i will contact the PM or Porject lead and explain the issues.

  First i wil concentrate which are the mandatory issues need to fix, even though the they are having high sev or low priority Or Low sev and high priority.

If most of the issues were solved then no problem, or if still open issue are there then i will mention in build release note...


CNU

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 23rd, 2009

 

Scenario:  As I understand this issue, we are testing what ought to be a release candidate build but there are 5 high and 5 low severity defects remaining and the client is pressing for its release to production.

This thought-provoking question appears to be from the Harvard Business School of Quality Assurance.   

This is what I would do:

1) I would quickly set up a meeting and discuss our circumstances with the Project Manager, Business Analyst, representatives from engineering and other key stakeholders in the company.  In this meeting, I would ask for their opinions. 
 

2) I would learn about our contractual agreements with the client and how our predicament plays out if we do what the client wishes.

3) I would obtain estimations on the time it will take to fix each of the 10 defects.

4) I would work with our cross-functional groups to find the solution that best serves our company as well as our client.

5) Then I would discuss all 10 defects with the client perhaps with Project Manager and an engineering rep in attendance.  Together we would determine the impact that each defect could potentially have on the client's customers and business and we would re-prioritize them accordingly.  In this meeting, I would keep an open mind and try as best I can to reach a mutually-agreeable solution that everyone can live with. 

naveenanand

 Profile Answers by naveenanand 

• Nov 11th, 2010

 

In such situations, as a senior person in the testing department.
First of all I will inform the situation to the project manager of the development team and inform him about the present situation and try to give him fullest information about the issue.

I am pretty much confident that I will convince him and together both the development and testing team will work together and has to come out with a solutions and give the client TAT when exactly the build will be released. This should be perfect otherwise client will not be happy even though you give him perfect one.

Definitley of all those 10 bugs severity plays the major role and inform the client about those things and inform him about your strategies for giving him perfect one.
Inspite of this if you give him wrong status and deliver the defect build.
Then client will never come to you.
Once this is done then this has to be intimated to higher manager and this will be done by development project manager.

Hope this will be fine to some extent and this would be like experience in another project.

mithr17

 Profile Answers by mithr17 

• Nov 17th, 2011

 

@ the person who posed this question:
"If you are the senior test engineer, you are getting pressure from the client to give the build." What did you mean by "give the build" ???

As I understand you wanted to ask what if the client is pressurizing you to sign-off on the release candidate, so here is my answer:

- Look at the priorities for the 10 bugs in question.

- Get an estimate from dev team to fix each bug including the low severity ones. What if the low severity ones have high priority?

- Check if extra QA and dev resources can be brought into this project if the client is not willing to shift the timelines. 6 out of 10 times, the client might have committed to the deadline than the budget, other times it may be both budget and deadline.
- If the client is willing to stretch the budget, estimate the extra dev and QA resources required to meet the deadline.

- Prepare a document outlining risks associated with each bugs and the impact they have on the brand, business and revenue of the client. The tone of the document must be in money and # hours. Clients always think in terms of money and this is an easy route to convince them not to go live. Point out with which features are these bugs associated and how much more time is required for effective regression testing.

- Hold a meeting with project stake-holders and present them your risks document. Point out how much extra time and money it will cost to fix the bug after the application goes live aside from lost revenue.

- As "kurtz182" mentioned you need to look into SLAs and look at the legal consequences of going live with buggy functionality.

- Ask PM to hold a meeting with client and present them the risks and impact document and negotiate with the client. Convince the client that although it may shoot up the budget or timelines now, but there is grave danger in going live WITH the bugs, not to mention the extra time that would be spent in meeting to re-visit the bugs in future.

- All this should get into the head of the client. If not, one of the top-guns in your company - Account manager or the CIO - will email the client that everyone had done lot of analysis and published the results to them (the client) and yet it was the client's decision to go live, therefore you company bears no responsibility, including legal, of it.