The point during software development when testing should start.
The body of knowledge used for test analysis and design.
The source to determine the actual results from a set of tests.
The method used to systematically devise test conditions.
Providing information for decision making.
During the planning activities.
During the implementation and execution activities.
During the monitoring activities.
During all the activities.
A developer makes a mistake which causes a defect that may be seen as a failure during dynamic testing.
A developer makes an error which results in a failure that may be seen as a fault when the software is executed.
A developer has introduced a failure which results in a defect that may be seen as a mistake during dynamic testing.
A developer makes a mistake which causes a bug that may be seen as a defect when the software is executed.
A tester finds a defect and reports it.
A tester retests a fix from the developer and finds a regression.
A developer finds and fixes a defect.
A developer performs unit testing.
It is a form of stress testing.
It is not feasible except in the case of trivial software.
It is commonly done with test automation.
It is normally the responsibility of the developer during unit testing.
The root cause is the old equipment and the effect is the new equipment.
The root cause is the customer complaints and the effect is the social media postings.
The root cause is conducting the testing on the wrong version of the equipment and the effect is the customer complaints and postings.
The root cause is the software failing on the later model and the effect is the customer complaints.
Traceability between the test cases and the requirements.
Coverage of the risk items by test case.
Traceability between the requirements and the risk items.
Coverage of the requirements by the test cases that have been designed.
Unit and integration.
Integration and system.
System and acceptance.
Testing involvement starts when the code is complete.
The test process is integrated with the development process.
The software is built in increments and each increment has activities for requirements, design, build and test.
All activities for development and test are completed sequentially.