![](/olcweb/styles/shared/spacer.gif) |
1 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) In software quality assurance work there is no difference between software verification and software validation. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
2 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The best reason for using Independent software test teams is that |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | software developers do not need to do any testing |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | strangers will test the software mercilessly |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | testers do not get involved with the project until testing begins |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | the conflicts of interest between developers and testers is reduced |
|
|
![](/olcweb/styles/shared/spacer.gif) |
3 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) What is the normal order of activities in which traditional software testing is organized? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | integration testing, system testing, unit testing, validation testing. |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | unit testing, validation testing, system testing, integration testing |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | unit testing, integration testing, validation testing, system testing |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | validation testing, system testing, integration testing, unit testing |
|
|
![](/olcweb/styles/shared/spacer.gif) |
4 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) By collecting software metrics and making use of existing software reliability models it is possible to develop meaningful guidelines for determining when software testing is done. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
5 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following strategic issues needs to be addressed in a successful software testing process? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | conduct formal technical reviews prior to testing |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | specify requirements in a quantifiable manner |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | use independent test teams |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | wait till code is written prior to writing the test plan |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | a and b |
|
|
![](/olcweb/styles/shared/spacer.gif) |
6 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following need to be assessed during unit testing? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | algorithmic performance |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | code stability |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | error handling |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | execution paths |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | c and d |
|
|
![](/olcweb/styles/shared/spacer.gif) |
7 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Units and stubs are not needed for unit testing because the modules are tested independently of one another. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
8 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Top-down integration testing has as it's major advantage(s) that |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | low level modules never need testing |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | major decision points are tested early |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | no drivers need to be written |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | no stubs need to be written |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | b and c |
|
|
![](/olcweb/styles/shared/spacer.gif) |
9 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Bottom-up integration testing has as it's major advantage(s) that |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | major decision points are tested early |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | no drivers need to be written |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | no stubs need to be written |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | regression testing is not required |
|
|
![](/olcweb/styles/shared/spacer.gif) |
10 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Regression testing should be a normal part of integration testing because as a new module is added to the system new |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | control logic is invoked |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | data flow paths are established |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | drivers require testing |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | a and b |
|
|
![](/olcweb/styles/shared/spacer.gif) |
11 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Smoke testing might best be described as |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | bulletproofing shrink-wrapped software |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | rolling integration testing |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | testing that hides implementation errors |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | unit testing for small programs |
|
|
![](/olcweb/styles/shared/spacer.gif) |
12 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) When testing object-oriented software it is important to test each class operation separately as part of the unit testing process. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
13 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The OO testing integration strategy involves testing |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | groups of classes that collaborate or communicate in some way |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | single operations as they are added to the evolving class implementation |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | operator programs derived from use-case scenarios |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | none of the above |
|
|
![](/olcweb/styles/shared/spacer.gif) |
14 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Since many WebApps evolve continuously, the testing process must be ongoing as well. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
15 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Testing MobileApps is not different than testing WebApps. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
16 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The focus of validation testing is to uncover places that s user will be able to observe failure of the software to conform to its requirements. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
17 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Software validation is achieved through a series of tests performed by the user once the software is deployed in his or her work environment. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
18 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Configuration reviews are not needed if regression testing has been rigorously applied during software integration. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
19 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Acceptance tests are normally conducted by the |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | developer |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | end users |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | test team |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | systems engineers |
|
|
![](/olcweb/styles/shared/spacer.gif) |
20 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that software is able to continue execution without interruption. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
21 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
22 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Stress testing examines the pressures placed on the user during system use in extreme environments. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
23 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Performance testing is only important for real-time or embedded systems. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
24 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Debugging is not testing, but always occurs as a consequence of testing. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
25 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following is an approach to debugging? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | backtracking |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | brute force |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | cause elimination |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | code restructuring |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | a, b, c |
|
|