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
Hi all
Question itself wrong.because no developer will close the
bug. once developer accepts the bug then rectify the bug,
and then he will change the status as "fixed" instead of
closed as said in the question.
So Tester will verify in the next build
if it works fine --> make bug as verified or closed.
if it not works --> the tester will reopen the bug.
Regards
Anand
| Is This Answer Correct ? | 14 Yes | 1 No |
Answer / sanju
Any bug once closed cannot be reopened.Since in this case
if you observe properly a bug was raised in build 1 and was
recitified and closed in build 1 itself. So again bug was
found in buid 2 while doing regression testing So the bug
status should be New since occurance of bug might be due to
changes or modification done further to the software. So
Accept strongly that bug status should be NEw.
| Is This Answer Correct ? | 6 Yes | 1 No |
Answer / preeti
see iam into web testing and when we prepared the defect
sheet we have following categories
DEFECT-ID,BUILD-no,STATUS,TESCASE -
ID,SECTION,SUMMARY,DESCRIPTION,OWNER,REMARKS,DEVELOPERS_NAME
,DEVELOPERS-STATUS.
now when we send the defect sheet to developers with staus
new or open defect they can assign the status as Fixed in
DEVlOPER_Status its tseter to assign it as CLOSED after
reviweing the same,
now again the defect occur for another build
SO what we do is
Suposing the defect id wa D-01 for build 1.1 and was closed.
to differentiate the same defect with another build the
DEFECT-id becomes a section of earlier ID D-01-01 and
status goes to "REOPEN".
in this way devloper was also easy to find out who was
assigined to work on the same defect in there team. and who
fixed it,
YOU can't assign "NEW"
BUILDS keep on changing ,like if u will assign new for
every defect .Team can never be able to conclude how many
times the defects reoccured till the release of final build.
i hope iam clear if any doubts please mail me.
preeti@darshconsultancy.com.
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / vijay
Yes . The developer can not close bug . The bug has to be
close by the tester once the regression test has done.
The answer is NEW
Regards,
vijay
| Is This Answer Correct ? | 6 Yes | 3 No |
Answer / santosh kumar singh
At fisrt the developer can't close the bug .
if consider that also in the very first build
the status will new for bug.
once the bug is fixed next build is relase
the tester has to confirm that the bug is really
rectify or not if yes than he can set the status as closed.
but in our case the same bug raised so the staus will be
REOPEN .
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / venkat nagender
Bug raised in build 1 will be tested in build2 and move the
status of bug to verified by the tester.
But if the same bug present in the build2 also then it will
be moved from resolved (status change by developer) to
(status change by tester) reopen.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / divya raj
I agree with Santoshnathan, the status of the bug will be
new since its a different build. Also the status of the
defect is closed by the tester and not the developer,
Developer can however update the defect status as'fixed'.
| Is This Answer Correct ? | 2 Yes | 2 No |
pls i want test cases for telecom billing system
pliz anyone give suggest me the test cases for shorting numbers in asc/desc order.
what is not present in the test case? 1>requirment ID 2>test case ID 3>bug ID 4>objective
Explain the concurrency testing?
write test case for button of google page?"i am feeling lucky" if button is not appear on page?
regression testing falls under white box or black box testing?
consider a program module that inputs two (2) values, n and max, and computes the sum of the first n integers as long as this sum is less than max; otherwise an error should be reported. if n is negative, then it takes the absolute value. a) list the equivalence partitions, and b) list the boundary values.
explain with examples- transaction testing, syntax testing, domain testing, logic testing, and state testing.
how to write test cases in interview exam like one website it contain a/c # text box, current bill amount text box,sms offer,calling offer,internet these 3 are list boxes and remindmelater,continue these 2 are buttons. and qu is like 1.user doesn't have any dues from past 90 days,2.whose bill amount >= rs2000 from past 6 months. use this 2qu write testcases.
Write a test case on a durability of an electric bulb and test it that it will last for next 10 months.
Write all test cases for Bus Pass Renewal
plz tell how to test this: We have to change the password of password field the condition is:The password will expiry after 30 days and that should not allow last 12 similar passwords....