Test Case Design

Test Design

1. A good test suite will include the following test(s)

a) Tests of normally occurring transactions
b) tests using invalid inputs
c) tests that violate established edit checks
d) A and B only
e) A, B, and C

2. Before performing volume testing, it is important to challenge each input and output data element, to determine potential limitations, and then document those limitations.

a) True
b) False

3. Before selecting which conditions you are going to include in your test suite, you should rank the test conditions according to risk.

a) Always true
b) True if there is a limited test budget
c) False

4.    Analysis of test results should include...

a) System components affected
b) terminal and onscreen outputs
c) order of processing
d) compliance to specs
e) all of the above

5.    Assuming you could reach 100% of any of the coverage types below, which one would leave the MOST potential for unexecuted code (and therefore, undiscovered errors)?

a) Modified decision coverage
b) global data coverage
c) statement coverage
d) branch coverage
e) decision/condition coverage

6.    When evaluating whether a test suite is complete (eg, doing a peer review or inspection), Which of the following should NOT be considered?

a) Whether the scripts have appropriate sign on and setup procedures
b) Whether the scripts address all items on each (onscreen) menu
c) Whether the scripts include data setup and other prerequisites
d) Whether the scripts test single transactions, multiple transactions, or both
e) all should be considered

7.    When performing volume testing, a small percentage of invalid data should be used.

a) True
b) False

8.    A Pseudoconcurrency test is a test that validates...

a) Data security when two or more users access the same file at the same time
b) file integrity
c) volume testing
d) A and B only
e) A and C only

9.    Which of these is not a good use of a code coverage analysis?

a) Simply to measure how well your test cases cover the code
b) analyze test coverage against system requirements
c) find "holes" in your testing and develop new test cases as supplements
d) start with black box testing, measure coverage, and use white box testing to test the remainder
e) All are good uses

10.    Stop procedures are important in scripting because...

a) The person executing hte script needs to know what kinds of errors would invalidate hte rest of the script
b) the person running the script needs to know if they can pick up the script on a later step after logging a bug
c) both of these

11.    Regardless of whether a script is manual or automated, it is important to consider:

a) Environmental constraints
b) think time
c) file states/contents
d) processing options
e) all of the above

12.    When developing your test suite, you should NOT:

a) Use transactions with a wide range of valid and invalid input data
b) use all forms of documentation to guide test cases and the data associated with them
c) start by testing one data point at a time so you can isolate the cause of defects, then move on to combinatorial tests
d) attempt to test every possible combination of inputs
e) you should do all four of the above