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 |
Explain the monkey testing?
ATM REQUIREMENT TO BE TRANSLATED INTO TEST PLAN AND TEST CASES ATM REQUIREMENT AS FOLLOWS: Requirements Statement for Example ATM System The software to be designed will control a simulated automated teller machine (ATM) having a magnetic stripe reader for reading an ATM card, a customer console (keyboard and display) for interaction with the customer, a slot for depositing envelopes, a dispenser for cash (in multiples of $20), a printer for printing customer receipts, and a key-operated switch to allow an operator to start or stop the machine. The ATM will communicate with the bank's computer over an appropriate communication link. (The software on the latter is not part of the requirements for this problem.) The ATM will service one customer at a time. A customer will be required to insert an ATM card and enter a personal identification number (PIN) - both of which will be sent to the bank for validation as part of each transaction. The customer will then be able to perform one or more transactions. The card will be retained in the machine until the customer indicates that he/she desires no further transactions, at which point it will be returned - except as noted below. The ATM must be able to provide the following services to the customer: A customer must be able to make a cash withdrawal from any suitable account linked to the card, in multiples of $20.00. Approval must be obtained from the bank before cash is dispensed. A customer must be able to make a deposit to any account linked to the card, consisting of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the ATM, subject to manual verification when the envelope is removed from the machine by an operator. Approval must be obtained from the bank before physically accepting the envelope. A customer must be able to make a transfer of money between any two accounts linked to the card. A customer must be able to make a balance inquiry of any account linked to the card. A customer must be able to abort a transaction in progress by pressing the Cancel key instead of responding to a request from the machine. The ATM will communicate each transaction to the bank and obtain verification that it was allowed by the bank. Ordinarily, a transaction will be considered complete by the bank once it has been approved. In the case of a deposit, a second message will be sent to the bank indicating that the customer has deposited the envelope. (If the customer fails to deposit the envelope within the timeout period, or presses cancel instead, no second message will be sent to the bank and the deposit will not be credited to the customer.) If the bank determines that the customer's PIN is invalid, the customer will be required to re-enter the PIN before a transaction can proceed. If the customer is unable to successfully enter the PIN after three tries, the card will be permanently retained by the machine, and the customer will have to contact the bank to get it back. If a transaction fails for any reason other than an invalid PIN, the ATM will display an explanation of the problem, and will then ask the customer whether he/she wants to do another transaction. The ATM will provide the customer with a printed receipt for each successful transaction, showing the date, time, machine location, type of transaction, account(s), amount, and ending and available balance(s) of the affected account ("to" account for transfers). The ATM will have a key-operated switch that will allow an operator to start and stop the servicing of customers. After turning the switch to the "on" position, the operator will be required to verify and enter the total cash on hand. The machine can only be turned off when it is not servicing a customer. When the switch is moved to the "off" position, the machine will shut down, so that the operator may remove deposit envelopes and reload the machine with cash, blank receipts, etc. The ATM will also maintain an internal log of transactions to facilitate resolving ambiguities arising from a hardware failure in the middle of a transaction. Entries will be made in the log when the ATM is started up and shut down, for each message sent to the Bank (along with the response back, if one is expected), for the dispensing of cash, and for the receiving of an envelope. Log entries may contain card numbers and dollar amounts, but for security will never contain a PIN.
How to write test cases on for Logging management?
Write a test case scenario for Web-based address book?
How to write a test cases for the following Please it is urgent Once user clicks that link Invite Friend page opens up thru which user can do 2 functions - first is to search friends detail(name, mail id) from her address book in other sites (india times, yahoo, gmail and rediff) and second to mail the invite to the selected person/s. User can send invite to multiple person at same time. Searching friends detail in other address books will work like this: - User will input name, email id, pwd etc, select from which site she want to get friends list and then click on Import. - Users address book from other sites will be imported in one shot(first time) to iDiva database. - It will be arranged in alphabetical order(complete list) and mail ids which are already used will be in different color. - User will be able to update her address book by clicking on ""Refresh"" button on the page, which will trigger the process again, and fetch new mail ids.
how to write test cases for credit card payment
Generally when we are writing test cases we give headings as Case id , description, input values, expected, actual, severity and priority and pass/fail. is there any seperate profama during testing the web site manually. (guys it very urgent for me in my office can any one help me plz)
Write negative test case for logout????? Answer soon friends
what is the purpose of writing testcases
Consider the following: Pick up and read the newspaper Look at what is on television If there is a program that you are interested in watching then switch the the television on and watch the program Otherwise Continue reading the newspaper If there is a crossword in the newspaper then try and complete the crossword A. SC = 1 and DC = 1 B. SC = 1 and DC = 2 C. SC = 1 and DC = 3 D. SC = 2 and DC = 2 E. SC = 2 and DC = 3
For a Login screen with Username, Password input fields and Enter, Cancel button write Test Cases for GUI, Funcitonal, Negative, Usability and Security testing.
why we need a test plan