Reducing the amount of overtime need to finish the project on time.
Receiving compliments from the users on the aesthetic aspects of the tool.
Measuring the satisfaction of management fro staying within the scope.
Assessing whether the benefits will be achieved at reasonable cost.
I ,iii, iv
I, ii, iv
Ii and iv
The required level of confidence has been achieved.
Time runs out.
No more faults are found.
The user's won't find any serious faults.
Boundary value analysis
Black-box is functional; white-box is non-functional.
Black-box is structural , white-box is functional.
Black-box is functional or non-functional , white-box is structural .
Black-box can only be performed after white-box
The reviewing of test plans.
The analysis of program code.
The analysis of batch programs.
A black-box testing technique.
100% decision coverage is achieved if statement coverage is greater than 95%.
100% statement coverage = 100% decision coverage
100% statement coverage is achieved if decision coverage is greater than 90%
100% decision coverage always means 100% statement coverage
Both are widely used as formal techniques.
Both are white-box testing techniques.
Both are experienced-based techniques.
Both are static testing techniques.
A3, B1, B2, B4
A1, A4, C3, D2
A2, D4, A1, D1
A2, A3, A4, B1
Decision table testing
Boundary value analysis
State transition testing
How to fix a fault.
How to reproduce the fault.
Test environment details
The actual and expected outcomes.
I, ii , iii are correct and, iv is incorrect.
I, iv are correct and ii and iii are incorrect.
Ii, iv are correct and i ,iii are incorrect.
Ii, iii, iv are correct and i is incorrect.
Deciding on execution of reviews
.Documenting all the issues and problems.
Follow-up after the review meeting
Identifying and describing the findings
I, iii, iv
I, v, vi
I, ii, vi
I, iv, vi
Component testing, integration testing, re-testing, regression testing
Component testing, acceptance testing, system testing, usability testing
Component testing, integration testing , system testing, acceptance testing
Integration testing, system testing, alpha testing, beta testing
Gives information about what code has and has not executed.
Can detect memory leaks.
Checks expected results against actual results.
Gives quality information about the code without executing it.
Here's an interesting quiz for you.