A collection of independent, reusable test cases.
A technical document that describes the various symptoms or failure modes associated with a single bug.
A deliverable that details the strategic approach to a testing effort
A & B
A description of the relationship between two or more variables or set members in which the value of one does not influence the values of others.
Any ill-advised, substandard, or temporary fix applied to an urgent problem in the (often misguided) belief that doing so will keep a project moving forward.
The process in which developers determine the root cause of a bug and identify possible fixes
A mismatch between the program and its specification.
The domain of possible inputs is too large to test .
Limited financial resources .
There are too many possible paths through the program to test
The user interface issues (and thus the design issues) are too complex to completely test.
All the planned tests have been run
Time has run out
All faults have been fixed correctly
Both a) and c)
It depends on the risks for the system being tested
Complete testing of software is attainable if you have enough resources and test tools
With automated testing you can make statements with more confidence about the Quality of a product than with manual testing
For a software system, it is not possible, under normal conditions, to test all input and preconditions
A goal of testing is to show that the software is defect free.
Evaluating exit criteria and reporting
Implementation and execution.
Planning and control.
Analysis and design.