Question 1 Why test outputs one at a time? Why not test a bunch of them at once?   Show Answer Previous Question        Next Question Done With Exercise                         Question 2 Where do you get the information about which inputs an output depends on? List the possibilities from best to worst choices.   Show Answer Previous Question        Next Question Done With Exercise                           Question 3 How can you increase your confidence that a given output doesn't depend on any inputs other than the ones that you think it does?   Show Answer Previous Question       Next Question Done With Exercise

 

Question 1 - Answer An output is correct when it's always right, under any combination of input conditions. If we "test" many outputs at once, we can't be sure that we've covered all the bases - that is, all the relevant combinations of inputs. Secondly, testing the outputs one at a time lets us vary the intensity of testing according to how critical each output is, rather than treating all the outputs as equally important.   Previous Question | Repeat Question | Next Question Done with Exercise                           Question 2 - Answer First choice is the users, if any. They really know the application. Next choice would be the specs, if any, followed by the designers, programmers, and the code itself. The code is a particularly last-ditch place to get this information because the code is what we're testing.   Previous Question | Repeat Question | Next Question Done with Exercise                       Question 3 - Answer The Twinkling technique will increase the confidence to any desired level.   Previous Question | Repeat Question | Next Question Done with Exercise

Copyright © 1998 - 2005 by The Testing Center. All rights reserved. Images digitally watermarked.