Software Test 2 - Software Testing Strategies
A
Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration. A) True B) False
A
Since many WebApps evolve continuously, the testing process must be ongoing as well. A) True B) False
B
Smoke testing might best be described as A) bulletproofing shrink-wrapped software B) rolling integration testing C) testing that hides implementation errors D) unit testing for small programs
B
Software validation is achieved through a series of tests performed by the user once the software is deployed in his or her work environment. A) True B) False
B
Stress testing examines the pressures placed on the user during system use in extreme environments. A) True B) False
B
Acceptance tests are normally conducted by the A) developer B) end users C) test team D) systems engineers
C
Bottom-up integration testing has as it's major advantage(s) that A) major decision points are tested early B) no drivers need to be written C) no stubs need to be written D) regression testing is not required
A
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. A) True B) False
B
Configuration reviews are not needed if regression testing has been rigorously applied during software integration. A) True B) False
A
Debugging is not testing, but always occurs as a consequence of testing. A) True B) False
B
In software quality assurance work there is no difference between software verification and software validation. A) True B) False
B
Performance testing is only important for real-time or embedded systems. A) True B) False
B
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. A) True B) False
B
Regression testing should be a normal part of integration testing because as a new module is added to the system new A) control logic is invoked B) data flow paths are established C) drivers require testing D) all of the above E) both a and b
A
The OO testing integration strategy involves testing A) groups of classes that collaborate or communicate in some way B) single operations as they are added to the evolving class implementation C) operator programs derived from use-case scenarios D) none of the above
A
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. A) True B) False
E
Top-down integration testing has as it's major advantage(s) that A) low level modules never need testing B) major decision points are tested early C) no drivers need to be written D) no stubs need to be written E) both b and c
B
Units and stubs are not needed for unit testing because the modules are tested independently of one another. A) True B) False
A
When testing object-oriented software it is important to test each class operation separately as part of the unit testing process. A) True B) False
E
Which of the following is an approach to debugging? A) backtracking B) brute force C) cause elimination D) code restructuring E) a, b, and c
E
Which of the following need to be assessed during unit testing? A) algorithmic performance B) code stability C) error handling D) execution paths E) both c and d
E
Which of the following strategic issues needs to be addressed in a successful software testing process? A) conduct formal technical reviews prior to testing B) specify requirements in a quantifiable manner C) use independent test teams D) wait till code is written prior to writing the test plan E) both a and b
