(questions asked in interview)hi every one can any one
please answer to this questions.these questions were asked
in an interview.i have another interview next week . 1.when
the time schedule is tight how will you approch the
testing,and the relese is nearing and we need to finish
testing how can we follow in that case.do we need to exicute
all the test cases or can priortise and leave some to next
relase. 2. when a new feature is added to the existing
application we need to add new test cases but after that do
we need to change all the existing test cases and while
running do we need to exicute entire application test cases
or only the new feature test cases and related new feature
test cases. 3.do you have any situation where you have to
write and exicute the test cases same time, how will you
follow.does it happens in real time. 4.example of bug which
is not reproducible.like tester say that there is bug and
developer say no can some example of such bugs. 5.during
regression testing some times do we need to add new some
additional test cases to test that bug.
Answers were Sorted based on User's Feedback
Answer / venkat
1. You have to test the major functionalities which has
largest impact on the project.
2.When a new feature is added you have to test all the
dependent modules. If no dependent modules are there then
we have to do 30 to 40% regression testing. If the whole
product has impact because of this feature then you have to
test the whole.
3.In real time it doesn't happens. Once the testcases were
written review will happen, once the review was ok then we
start testing.(Still now I never faced such situation.
Anyone plz correct me If I am wrong).
4.Generally in GUI applications these types of error
occurs. Generally we dont remember what are all we clicked.
In such situations we cant reproduce the bug.
5.No
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / raja
For 1 question, we need to follow the following steps:
1. First we need to cross with PRS (Project release sheet)
to make sure what are all the requirements we are going to
deliver.
2. We need to go Sanity testing to conform whether all the
Functional and UI related Test cases are passing or not.
3. If we find and issues in the currect build, directly we
need to inform to the concern application developer and then
we need to raise a bug in bug tracking tool.
4. Once we exist the Sanity testing, we need to go for
Happy/random tesiting to make sure all the fuctionality is
working fine are not.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / chinmay
hi Friend
For above 5 points for the 1st what i say is : when the time
is near to release then we need to perform testing only on
the test case which are of very high important,such as
,checking all the function are working properly or not,
field are accepting correct data which is required...and
many more...what u do not test at this point of time is the
DESIGN and the USER INTERFACE (mean to say is the appearance
of the application) but then it does not mean that is should
be not readable....
so hope u will have much points to put forward to the person
how is taking yur interview.
| Is This Answer Correct ? | 0 Yes | 1 No |
Can any1 tell me how to do and Integration test design and test cases for Order Inventory system for use cases. ALso how is that going to differ from System Testing. The system is similar to amazon.com online ordering system and you can place order by calling customer call center.
How would you do " Keeping two folders in sync testing"
0 Answers ABC, HCL, Microsoft,
how to execute test cases manually
There is project earlier it was developed in VB then they had replaced the project by java and there is no documentation available then how you are going to check that project. (Hint: - Parallel Testing).
can anyone send me a copy of a business requirement and test cases attributed to such requirent. thank u
I have register form there is first name field.what will be the steps to execute test case???
Explain the exactly meaning of test case?
Explain the format of a requirement traceability
Do you write test plan and test case?
Explain the domain testing?
What is p0,p1,p2,p3 in software tesing
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.