Answer / divya

In this question, you have to answer only from perspective
of QA so then the answer would be 1>Reopen
you have to tell the developer that since it is not fixed in
build 1 have to reconsider and fix in build 2...

Answer / varun

reopen is the status of the bug

Answer / anand

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

Answer / mudassar

Reopen is the correct answer

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.

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.

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

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 .

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.

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'.

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

1 Answers  

test cases for login window

1 Answers  

Can any one send me the Sample sanity Test Cases??? Mail id:veerabhadrudu.p@gmail.com

0 Answers   TCS,

In any Hyderabd institute you can find these word commomly used by faculties ... Yes or no / Right or wrong so funny...

0 Answers  

i need sample case of Login window of USER NAM, PASSWORD It is very urgnt

12 Answers   CSC,

my namjad . firefox doesn't open yahoo page but other page open so what is reason I'm again install but is not working

3 Answers   Wipro,

1.1 Purpose This tool is also a simple tool, but will be graphics- intensive, and will access the 3 databases (card databases) used in Tarot. 1.2 Scope Only for registered user. 1.3 User Interface - No questions asked, parrot pulls out tarot card - Inside Parrot application, User just have to click on a link saying ""XXXX"" to activate the tool. - Shown is the card of the day, from pack of Tarot cards(78 in number) with fixed graphics, animation, audio. Output: - Graphic-rich display of randomly selected card with detailed meaning, with links to tarot tool. - Graphics: Flying / walking parrot, emerging and choosing a card, displaying the same, and continuing to interact based on card meaning. - The cards also need to carry a brief 1/0 meaning, which will trigger a 1/0 behavior from the parrot (sympathy/making fun/crying or congratulating/smiling/winking)

0 Answers  

How to write test cases for manual testing? What are the main syntex for writing test cases for Junit?

0 Answers   Wipro,

what are the sanity test cases for a waterBottel?

6 Answers  

plz.. tell me hw to write the Use Case for Online Purchase... just tod. itself i need...

0 Answers  

Do we have to write the seperate test cases for System testing and UAT testing? And also what are the roles and reponsibilities of a tester/how to interact when End users are performing the UAT Testing.

0 Answers  

How to write test scenarios for a Web application, with an example?

3 Answers   Deloitte, LiveTech, TCS,