Black box testing treats the software as a "black box"—with proper knowledge of internal implementation
Black box testing treats the software as a "black box"—without any knowledge of internal implementation
Black box testing is a testing process with sufficient knowledge of internal implementation
None of the above
Creating test suites from the test cases
Executing test cases either manually or by using test execution tools
Comparing actual results
Designing the tests
White Box Testing
Block Box Testing
When the code is complete
When the design is complete
When the software requirements have been approved
When the first code module is ready for unit testing
Check user friendliness
Improve software accuracy
It includes the verification of designs.
It states that modules are tested against user requirements.
It specifies the test techniques to be used.
It only models the testing phase.
When the specified number of faults are found.
When the test completion criteria are met.
When all high and medium priority tests are complete.
When all statements have been executed.
This is an acceptable risk of a multi-user system.
Insufficient functional testing has been performed.
This indicates an important non-functional requirement was not specified and tested.
It is not possible to test against such events prior to release.
Incorrect or missing functions
All of the above
None of the above
Performed by customers at their own site
Performed by customers at the software developer's site
Performed by an independent Test Team
Performed as early as possible in the life-cycle
Finding faults in the system
Ensuring that the system is acceptable to all users
Testing the system with other systems
Testing from a business perspective
Measuring response times
Simulating many users
Generating many transactions
It is easy to execute.
It is designed to detect faults if present.
The expected outcome is specified before execution.
It is unlikely to delay progress.