If we found a bug but that bug is not accepted by developer then what u do.

Answers were Sorted based on User's Feedback



If we found a bug but that bug is not accepted by developer then what u do...

Answer / jenitta

if dev team nt accepted d bug means,once again we have to
chk,whether it is correct bug r nt,and also should chk
environment,bcoz may be dev team using different
environment,and we using dif environment.in dat situation
also bug wil rise.if we found no environment pbm den take
screen shots of dat page and send to dev team and explain
the bugs to dev team

Is This Answer Correct ?    36 Yes 0 No

If we found a bug but that bug is not accepted by developer then what u do...

Answer / sonal

I will plan a meeting to discuss regarding the concerned
bug(s) as there could be one of the following situations-

1. The steps taken for out-coming of the bug may be different.

2. The environment variables (e.g. browser, OS etc) may differs.

3. Being a tester I will try to have screenshots or if don't
have then will re-produce the bus and take screenshot to
report the bug more specifically.

4. If still we will not come to any decision then this
matter has been left to the seniors.

Hope my answer would be satisfactory.

Is This Answer Correct ?    6 Yes 0 No

If we found a bug but that bug is not accepted by developer then what u do...

Answer / padma

From the question, one can understand that the stage of the
testing is Unit

testing,because developer is involved.,and it is 'bug' and
not a 'defect'.
in this scenario,Code reviews can be conducted.
Generally unit testing will be done by developers.Because
bugs found at unit

level,are raised by the developers.IF developer says it is
not a bug, then it

will be considered as issue in the code review.
Whatever raised during the testing will be considered as
defects later on, in

which developer will not be involved.
During the integration testing,if the units are reviewed and
unit tested only

then integrated if it does not create new issues or defects.
if developer says it is not a bug, then tester will say it
is a defect in later phases of testing

Is This Answer Correct ?    2 Yes 1 No

If we found a bug but that bug is not accepted by developer then what u do...

Answer / sp

According to bug life cycle,each bug that is not
accepted/rejected will holds a description/notes/comments
for non-acceptance from the owner of the unit or developer.

In bug life cycle we do not have any status for bug such as
'Accepted'.
but most of the tools contain statuses as
New,open,Assigned,fixed,closed.

When you have a bug tracking tool, the tester's concern is
see the bug status either one of these,New, open, assigned,
fixed,or closed.But there is no status such as 'Accepted'
status to the tester's view.It is the job of the one who
assigns the bugs to the developer, not a tester for whom the
tool settings will differ from the developer and tester such
as management.

Developers environment is definitely differs from test
environment, because testing always be conducted on holistic
environment that is preferred for the AUT, (application
under test) as well as user.

Will go for reproducing the bug for n number of
occurrences,before declaring it as a bug.
If it is not found at the development environment,
check the bug is duplicate of earlier fixed-->closed bugs in
which case it will not be accepted by the developer.
most of the units when integrated, bugs will not be accepted
by the developer because it is found while integration and
cannot be fixed as a unit,in which case cannot be accepted
by the developer.

Is This Answer Correct ?    0 Yes 0 No

If we found a bug but that bug is not accepted by developer then what u do...

Answer / hanu424

Hi,

Either dev is failed to understand the requirement or QA is failed to understand the requirement. Then go to requirement document and check whether the bug is posted based on the requirement or not. if both are same then QA will take a screen shot for both and show them to dev team. if the bug is not related to requirement, then discuss with test lead and go further action, means that bug will be closed.

Is This Answer Correct ?    0 Yes 0 No

If we found a bug but that bug is not accepted by developer then what u do...

Answer / balakiran

I'll Escalate to test Lead...

Is This Answer Correct ?    3 Yes 10 No

Post New Answer

More Manual Testing Interview Questions

what is data base testing, explain with example

4 Answers  


What types of software testing are available?

0 Answers  


How do you manage your writen/modified/executed test cases, Bug report etc,without using any tool?

1 Answers  


Being an Manual tester, what will be the role or activity in test plan ?

0 Answers  


In the Testing, How do we find the Duplicate Defects. In the case of testing is going on On-site r off-shore..some times on site and off-shore people may enter defects at the same time..those may include duplicate defects. how we have to find those defects..

1 Answers   ACS,






What made you pick testing over another career?

1 Answers  


What is the role of documentation in QA?

1 Answers   IBM,


types of reviews?Advantages of reviews? Diff between process and procedure? diff b/w verification and validation? diff b/w cmm,cmmi? exp tqm,gqm,iso,ieee? Roles and responsibilities of tester? Ricks,types of ricks? what r Quality factors?

0 Answers   Semantic Space,


Why you developed the software to test the software?

2 Answers   Fulcrum Logic,


what is 'v'model?

6 Answers  


Data flow testing is a control structure testing technique where the criteria used to design test cases is that they Option 1 Rely on basis path testing Option 2 Exercise the logical conditions in a program module Option 3 Select test paths based on the locations and uses of variables Option 4 Focus on testing the validity of loop constructs

1 Answers  


Tell me about SOFTWARE DEVELOPMENT LIFE CYCLE? Explain in brief?

1 Answers  


Categories