build 1 bug is raised and it was closed by developer and
build 2 is released in build 2 also same bug raised what is
the satus of that bug.
1>reopen 2>open 3>new 4>defered
Answers were Sorted based on User's Feedback
Answer / sherin
According to me, The answer is 'New'.
As the bug is raised in build 2, the bug should have
occured because of some modifications that was done in
build 2 and not because of build 1(which is closed).So it
clearly shows that the bug is a new one.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / santoshnathan
hai divya,varun,Mudassar,
am sorry to say this.You please study the question
carefully and don't get confused.OK.
Actually once bug is raised in build 1 then Bug status will
be NEW(status),after that if the developer is accepted that
is real bug,then only bug is ASSIGNED(Status) to concerned
developer.After fixing the bug,again it comes to tester in
the form of Build 2.In this build 2 tester performs testing
on that bug whether it is fixed or not.Once tester get
confirmed that it is fixed,then that bug is
closed(Status).Closed in the sense functionality working
fine without any side effect.This is the story.
Then come to your answers,You people tell me one thing.
How can you say that,see question carefully.Is it possible
to raising and closing the bug in the build 1.Definitely
not,why because bug raised in build 1 and assigned to
developer,he fixes the bug and release the build 2(modified
build).On that tester will test, if it fixed then tester
will close the bug in build 2(modified build).
OK.
You people please remember that,
bug cycle:if the bug is found in build 1 the status will be
STEP 1.NEW
STEP 2.ASSIGNED(ACCEPTED)
STEP 3.FIXED and modified build released(BUILD 2,3,4 like
that)is sent to TESTING
STEP 4.VERIFICATION BY TESTER
STEP 5.IF IT FIXED,THEN BUG CLOSED(in build 2(modified
build) not in build 1)
STEP 6.IF NOT FIXED,then here status changes as REOPEN
STEP 7.repeat from STEP 2 TO STEP 5 UNTIL IT IS CLOSED.
After closing the bug in build 2,then you no more concern to
build 1.so,last but not least,my conclusion is that, Again
same bug is raised in build 2,then the status will be
NEW,not in REOPEN status.
Anwser to the above question is ,In build 1 bug is raised
and closed.And again in build 2 the same bug is raised,it
means that either developer may not work on that (OR)tester
may not verified correctly.
I hope you may understand.Am sorry to tell u this long story.
any quires please send to santoshknathan@gmail.com
| Is This Answer Correct ? | 7 Yes | 9 No |
Answer / nirman
Hey...Here closing that bug doesn't mean that particular
issue is not the bug....closing means developer agreed that
this is a bug but he does'nt want to fix it due to any
reason but if tester wants it to be fix in next release due
to customer impact or any other reason, he can reopen it.
So ans is 1-reopen.
| Is This Answer Correct ? | 0 Yes | 2 No |
Can you list down a few characteristics of a test case?
What we do when the Requirements are continuously changed?
A wholesaler sells printer cartridges. The minimum order quantity is 5. There is a 20% discount for orders of 100 or more printer cartridges. You have been asked to prepare test cases using various values for the number of printer cartridges ordered. Which of the following groups contain three test inputs that would be generated using boundary value analysis?
how to write test cases for credit card payment
Imagine that hotmail is the application taht ur going 2 test write 10 critical test case to test it ?
test cases for landline phone
what is login and login in testcases we write in testcaseid
While creating test data for testing an application, where exactly test data should be crated as in excel file or can we crate test data in database ?
Write a test case for telephone?
if u have a application that is demo verson and u want to perches it if u have full version. Plz give me some test case for try to break the applicatin
ATM application ( scenarios ): Analysis and testcases
Dear Friends, please send me some links where i will get all type of web driver programs.