Will always be automated
Will help ensure unchanged areas of the software have not been affected
Will help ensure changed areas of the software have not been affected
Can only be run during user acceptance testing
Top-down integration
Bottom-up integration
None of the above
Module integration
To ensure that all of the small modules are tested adequately
To ensure that the system interfaces to other systems and networks
To specify which modules to combine when and how many at once
To ensure that the integration testing can be performed by a small team
To specify how the software should be divided into modules
1000, 5000, 99999
9999, 50000, 100000
10000, 50000, 99999
10000, 99999
9999, 10000, 50000, 99999, 10000
S = 4, t = 3, u = 2 and 5, v = 1
S = 4 and 5, t = 3, u = 2, v = 1
S = 1 and 5, t = 3, u = 2, v = 4
S = 5, t = 4, u = 3, v = 1 and 2
S = 4 and 5, t = 1, u = 2, v = 3
1 test for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage. 3 for branch coverage
3 tests for statement coverage, 3 for branch coverage
3 tests for statement coverage, 2 for branch coverage
Test items
Test deliverables
Test tasks
Test environment
Test specification
True
False
Testing Planning
Test Control
Test analysis and design
Test implementation
1 and 2
1, 2 and 3
1, 2, 3 and 4
2 and 4
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.