CH14 (test bank) Flashcards
T/F: Testing and construction should be done independently of each other.
F
T/F: Acceptance testing is an informal activity in most development projects.
F
T/F: Due to design principles for object-oriented systems, such as cohesion and coupling, integration testing is usually a straightforward process with little complexity.
F
T/F: Frequent customer payments for new systems are tied to specific acceptance tests.
T
T/F: In complex data conversions programs must be constructed and tested in the same manner as operational software.
T
T/F: The purpose of system documentation is to help the end users understand the details of how the system works.
F
T/F: How to start up the system and how to shut it down are examples of system documentation.
F
T/F: Describing program functions required to implement specific business procedures is an example of user documentation.
T
T/F: Top-down and bottom-up development order cannot be applied to object-oriented designs (OODs).
F
T/F: The primary advantage of direct deployment, as compared to other installation methods, is minimal risk to business operations.
F
T/F: Parallel deployment is generally best when the consequences of a system failure are severe.
T
T/F: There is no one single method for performing phased deployment.
T
T/F: Partial parallel deployment and operation always entails the risk that significant errors or problems will go undetected.
T
T/F: Older production versions should not be overlapped with test versions of future production releases.
F
T/F: Beta versions do not need to be stored after the production version is released.
F
T/F: In some deployment situations, it may be possible to begin operation of the new system without converting data from the old system.
T
Which of the following is NOT a condition describing a test case?
a. An ending state or response
b. One or more events to which the software must respond
c. A set of input data
d. A starting state
c. A set of input data
The goal of _______ is to identify and fix as many errors as possible before units are combined into larger software units.
a. user testing c. integration testing
b. unit testing d. stress testing
b. unit testing
Which is NOT a responsibility of a test driver?
a. Receives output values c. Links to the unit to test
b. Issues a call to the unit to test d. Set input parameter values
c. Links to the unit to test
____ testing tests the behavior of a group of modules or methods.
a. Driver c. System
b. Integration d. Unit
b. Integration
____ testing examines the behavior of an entire subsystem or independent subsystem with respect to technical and user requirements.
a. Driver c. System
b. Integration d. Unit
c. System
A(n) ____ test is a test performed to determine whether the system fulfills user requirements.
a. acceptance c. system
b. integration d. performance
a. acceptance
A build and smoke test is often performed how frequently?
a. Several times a week c. At least monthly
b. Weekly d. Before going live
a. Several times a week
The primary purpose and benefit of a build and smoke test is to _______ .
a. test major additions to the software c. test programmer expertise
b. test equipment malfunctions d. test integration problems
d. test integration problems
A stress test is also called a _____ test.
a. throughput c. volume
b. performance d. equipment
b. performance
Complex modifications to database structure for a new system may require ____ the data after the changes.
a. testing c. reloading
b. deleting d. indexing
c. reloading