Chapter 2 Testin Throughout the Software Development Lifecycle Flashcards
Which of the following characteristics of good testing apply to any software development life cycle model?
A. For every development activity there is a corresponding testing activity.
B. Acceptance testing is always the final test level to be applied
C. All test levels are planned and completed for each developed feature
D. Testers are involved as soon as the first piece of code can be executed
A. For every development activity there is a corresponding testing activity.
Which of the following is a characteristic of well-managed test level?
A. It has a target duration of one month
B. It has a corresponding test objective
C. It does not overlap with another test level
D. It applies a single test design technique
B. It has a corresponding test objective
When should the testers start reviewing project documents?
A. When they have been baselined and approved
B. After the first revision
C. When the developers have started coding
D. As soon as draft is available
D. As soon as draft is available
What is important to do when working with software development models?
A. To adapt the models to the context of project and product characteristics
B. To choose the waterfall model because it is the first and best proven model
C. To start with the V-model and then move to either iterative or incremental models
D. To only change the organization to fit the model and not vice versa
A. To adapt the models to the context of project and product characteristics
Which one of the following describes the major benefit of verification early in the life cycle?
A. It allows the identification of changes in user requirements.
B. It facilitates timely set up of the test environment.
C. It reduces defect multiplication.
D. It allows testers to become involved early in the project.
C. It reduces defect multiplication.
Which iterative model consists of relatively short iterations (e.g. few weeks) and produces small features increments?
A. Rational Unified Process
B. Scrum
C. Kanban
D: Spiral (or prototyping)
B. Scrum
Which iterative model involves creating experimental increments, some of which may be heavily re-worked or even abandoned in subsequent development work
A. Rational Unified Process
B. Scrum
C. Kanban
D: Spiral (or prototyping)
D: Spiral (or prototyping)
Match every stage of the software Development Life cycle with the Testing Life cycle:
i. Hi-level design
ii. Code
iii. Low-level design
iv. Business requirements
a. Unit tests
b. Accetance test
c. System tests
d. Integration tests
A. i-d , ii-a , iii-c , iv-b
B. i-c , ii-d , iii-a , iv-b
C. i-b , ii-a , iii-d , iv-c
D. i-c , ii-a , iii-d , iv-b
D. i-c , ii-a , iii-d , iv-b
Where may functional testing be performed?
A. At system and acceptance testing levels only.
B. At all test levels.
C. At all levels above integration testing.
D. At the acceptance testing level only.
B. At all test levels.
Which testing level is primarily focused on building confidence rather than finding defects?
A. Unit Testing
B. Integration Testing
C. System Testing
D. Acceptance Testing
D. Acceptance Testing
Which one of the following is true of software development models?
A. There are always four test levels in the V-model.
B. In a Rapid Application Development (RAD) project, there are four test levels for each iteration.
C. In Agile development models, the number of test levels for an iteration can vary depending on the project.
D. There must be at least four test levels for any software development model.
C. In Agile development models, the number of test levels for an iteration can vary depending on the project.
In which test levels are the developers most heavily involved?
A. Compatibility
B. Acceptance
C. Component
D. Conversion
C. Component
Contract and regulation testing is a part of:
A. System testing
B. Acceptance testing
C. Integration testing
D. Functional testing
B. Acceptance testing
A test harness is a
A. A high level document describing the principles, approach and major objectives of the organization regarding testing
B. A distance set of test activities collected into a manageable phase of a project
C. A test environment comprised of stubs and drives needed to conduct a test
D. A set of several test cases for a component or system under test
C. A test environment comprised of stubs and drives needed to conduct a test
You are running a performance test with the objective of finding possible network bottlenecks in interfaces between components of a system.
Which of the following statements describes this test?
A. A functional test during the integration test level
B. A non-functional test during the integration test level
C. A functional test during the component test level
D. A non-functional test during the component test level
B. A non-functional test during the integration test level
Consider the following types of defects that a test level might focus on:
- Defects in separately testable modules or objects
- Not focused on identifying defects
- Defects in interfaces and interactions
- Defects in the whole test object
Which of the following list correctly matches test levels from the Foundation syllabus with the defect focus options given above?
A. 1 = performance test; 2 = component test; 3 = system test; 4 = acceptance test
B. 1 = component test; 2 = acceptance test; 3 = system test; 4 = integration test
C. 1 = component test; 2 = acceptance test; 3 = integration test; 4 = system test
D. 1 = integration test; 2 = system test; 3 = component test; 4 = acceptance test
C. 1 = component test; 2 = acceptance test; 3 = integration test; 4 = system test
Which of the following should NOT be a trigger for maintenance testing?
A. Decision to test the maintainability of the software.
B. Decision to test the system after migration to a new operating platform.
C. Decision to test if archived data is possible to be retrieved.
D. Decision to test after “hot fixes”.
A. Decision to test the maintainability of the software.
Which of the following statements are true in relation to component testing?
a. Stubs may be used.
b. May cover resource behaviour (e.g. memory leaks).
c. Tests the interactions between software components.
d. Defects are typically fixed without formally managing these defects.
A. a, c and d
B. a, b and d
C. b, c and d
D. a, b and c
B. a, b and d
Integration testing has following characteristics:
I. It can be done in incremental manner
II. It is always done after system testing
III. It includes functional tests
IV. It includes non-functional tests
A. I, II and III are correct
B. I is correct
C. I, III and IV are correct
D. I, II and IV are correct
C. I, III and IV are correct
Which one of the following statements about system testing is NOT true?
A. System tests are often performed by independent teams.
B. Functional testing is used more than structural testing.
C. Faults found during system tests can be very expensive to fix.
D. End-users should be involved in system tests.
D. End-users should be involved in system tests.
How is the scope of maintenance testing assessed?
A. Scope is related to the risk, size of the changes and size of the system under test
B. Scope is defined by the size and type of system being changed
C. Scope is defined by the size and type of system being changed
D. Scope is related to the number of system users affected by the change.
A. Scope is related to the risk, size of the changes and size of the system under test
The difference between re-testing and regression testing is
A. Re-testing is running a test again; regression testing looks for unexpected side effects
B. Re-testing looks for unexpected side effects; regression testing is repeating those tests
C. Re-testing is done after faults are fixed; regression testing is done earlier
D. Re-testing uses different environments, regression testing uses the same environment
E. Re-testing is done by developers; regression testing is done by independent testers
A. Re-testing is running a test again; regression testing looks for unexpected side effects
Which of the following statements comparing component testing and system testing is TRUE?
A. Component testing verifies the functionality of software modules, program objects, and classes that are separately testable, whereas system testing verifies interfaces between components and interactions between different parts of the system.
B. Test cases for component testing are usually derived from component specifications, design specifications, or data models, whereas test cases for system testing are usually derived from requirement specifications or use cases.
C. Component testing only focuses on functional characteristics, whereas system testing focuses on functional and non-functional characteristics.
D. Component testing is the responsibility of the testers, whereas system testing typically is the responsibility of the users of the system.
B. Test cases for component testing are usually derived from component specifications, design specifications, or data models, whereas test cases for system testing are usually derived from requirement specifications or use cases.
How can white-box testing be applied during acceptance testing?
A. To check if large volumes of data can be transferred between integrated systems.
B. To check if all code statements and code decision paths have been executed.
C. To check if all work process flows have been covered.
D. To cover all web page navigations.
C. To check if all work process flows have been covered.