-
Testing Approach
When you ask users to test software, what approach should they take?A. They should scan the user manual looking for situations of interest which they then test, menu option by menu option.B. They sit at the terminal, dreaming up situations randomly visiting all the features of the system to ensure they get broad coverage of the system.C. They work out what business processes are supported by the system,...
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 13th, 2009
The only reasonable answer is D) Users cannot test software effectively.
Users typically test a system during the Beta release of a product. Though companies should not rely only on this type of testing, it is useful in uncovering defects at little cost to the company. Throughout this period, users perform their day-to-day activities and are not thinking about product quality. They rarely if ever scan the user manual looking for situations of interest to test, so the answer is not A). They generally don't dream up situations randomly to visit all of the features of the system, so the answer is also not B). They don't have access to the company's business processes, so the answer is not C).mithr17
- Nov 1st, 2011
I still cannot understand why people are willing to waste time in posting already answered questions? Can you please use the search feature in this site and save everyone's time including yours? This does really anger a lot of people FYI
srinivasulub1981
- Nov 28th, 2009
HIAns D is correctThey will not have any idea of testing the softwareCNU
-
Faults Found by Users
Faults found by users in production are due toA. poor quality softwareB. poor software and poor testingC. bad luckD. insufficient time for testing
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 13th, 2009
Faults found by users in production are due to:
The best answer is B) poor software and poor testing
A) is true, but not as complete as B)
D) may also be true, but not as complete as B)
E) is obviously false because quality has nothing to do with luck
srinivasulub1981
- Nov 19th, 2009
HII feel it's due to poor quality, here the issue may come due to poor sw, but finding the issues is the major responcibility of a tester than dev team, but there that option was not there, so i can to the option B is correct, poor software and poor testingCNU
kurtz182
- Nov 13th, 2009
Faults found by users in production are due to:The best answer is B) poor software and poor testingA) is true, but not as complete as B)D) may also be true, but not as complete as B)E) is obviously false because quality has nothing to do with luck
-
Concurrency Testing
In what scenario concurrency testing is done? Give real time scenario for the same.
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 6th, 2009
Concurrency testing is performed when there are two or more scenarios being tested on the same application at the same time. A common form of concurrency testing takes place when two users are logged into the same application and a tester wishes to determine how their activities impact one another. It is commonly employed to test web sessions and state management.
srinivasulub1981
- Nov 28th, 2009
HIThis will be comes under Multi user testing, ie testing the application by more than one user at same time...The intention is find the behaviour of application when it was using by more than one user, ie to verify the speed, performance, how data base is responding, etcCNU
kurtz182
- Nov 6th, 2009
Concurrency testing is performed when there are two or more scenarios being tested on the same application at the same time. A common form of concurrency testing takes place when two users are l...
Testing Common Interview Questions
Read Best Answer
Ans