- A good test suite will include the following test(s)
Your answer:
tests of normally occurring transactions
tests using invalid inputs
tests that violate established edit checks
A and B only
A, B, and C
- Before performing volume testing, it is important to challenge each input and output data element, to determine potential limitations, and then document those limitations.
Your answer:
True
False
- Before selecting which conditions you are going to include in your test suite, you should rank the test conditions according to risk.
Your answer:
Always true
True if there is a limited test budget
False
- Analysis of test results should include...
Your answer:
system components affected
terminal and onscreen outputs
order of processing
compliance to specs
all of the above
- 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)?
Your answer:
modified decision coverage
global data coverage
statement coverage
branch coverage
decision/condition coverage
- When evaluating whether a test suite is complete (eg, doing a peer review or inspection), Which of the following should NOT be considered?
Your answer:
whether the scripts have appropriate sign on and setup procedures
Whether the scripts address all items on each (onscreen) menu
Whether the scripts include data setup and other prerequisites
Whether the scripts test single transactions, multiple transactions, or both
all should be considered
- When performing volume testing, a small percentage of invalid data should be used.
Your answer:
True
False
- A Pseudoconcurrency test is a test that validates...
Your answer:
data security when two or more users access the same file at the same time
file integrity
volume testing
A and B only
A and C only
- Which of these is not a good use of a code coverage analysis?
Your answer:
simply to measure how well your test cases cover the code
analyze test coverage against system requirements
find "holes" in your testing and develop new test cases as supplements
start with black box testing, measure coverage, and use white box testing to test the remainder
All are good uses
- Stop procedures are important in scripting because...
Your answer:
the person executing hte script needs to know what kinds of errors would invalidate hte rest of the script
the person running the script needs to know if they can pick up the script on a later step after logging a bug
both of these
- Regardless of whether a script is manual or automated, it is important to consider:
Your answer:
environmental constraints
think time
file states/contents
processing options
all of the above
- When developing your test suite, you should NOT:
Your answer:
use transactions with a wide range of valid and invalid input data
use all forms of documentation to guide test cases and the data associated with them
start by testing one data point at a time so you can isolate the cause of defects, then move on to combinatorial tests
attempt to test every possible combination of inputs
you should do all four of the above