rocky_garg11

 Profile Answers by rocky_garg11 

• Nov 12th, 2009

 

One of the most difficult fact is
A. Requirements are not clear. In such a case it is very difficult to test a software.
Others scenarios can not impact much on testing as a good tester can manage after reading the documents and have a necessary KT's from concerned persons.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 12th, 2009

 

The correct answer is A) The requirements/specifications are unclear.

B) is not correct because testers are rarely involved in the review of the requirements.

C) is not correct because it is the nature of software to provide little information about its internal state.

D) is not correct because requirements would describe in enough detail what the expected results should be, no matter how complex the software is.

Because B) through D) are not correct, then E) is obviously not correct as well.

A) is the only reasonable answer.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 19th, 2009

 

HI

The ans is :  A) The requirements/specifications are unclear.

For any of the project Requirements are like a heart to the body, so with out proper requirements, development/testing will become waste.



CNU

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Nov 27th, 2009

 

Answer) A. The requirements/specifications are unclear. is correct

B. Testers were not involved in the review of the requirements. (No Review is needed for the well known Application)
C. The software provides little information about its internal state. (Internal state is not neccesary once the functionality is well-known)
D. The software is so complex, it is difficult to calculate the expected results correctly. (What ever the software is too complex, different method is to evaluate the desired expected result)
E. All of the above.