Execution

Design

Planning

Check Exit criteria completion

Checking that we are building the right system

Checking that we are building the system right

Performed by an independent test team

Making sure that it is what the user really wants

White box

Black box

Green box

Yellow box

White box

Glass box

Structural

Functional

An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.

An inspection has a trained leader, whilst a walkthrough has no leader.

Authors are not present during inspections, whilst they are during walkthroughs.

A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.

Is not important

Increases as we move the product towards live use

Decreases as we move the product towards live use

Is more expensive if found in requirements than functional design

Can never be determined

As the first approach to deriving test cases

After more formal techniques have been applied

By inexperienced testers

After the system has gone live

Only by end users

Because incremental integration has better early defects screening and isolation ability

Because “big bang” integration is suitable only for real time applications

Incremental integration is preferred over “Big Bang Integration” only for “bottom up” development model

Because incremental integration can compensate for weak and inadequate component testing

As there are many different ways to test software, thought must be given to decide what will be the most effective way to test the project on hand.

Starting testing without prior planning leads to chaotic and inefficient test project

A strategy is needed to inform the project management how the test team will schedule the test-cycles

Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place.

Component testing should be performed by development

Component testing is also know as isolation or module testing

Component testing should have completion criteria planned

Component testing does not involve regression testing

As soon as the code is written

During the design stage

When the requirements have been formally documented

As soon as possible in the development life cycle

Because testing is good method to make there are not defects in the software

Because verification and validation are not enough to get to know the quality of the software

Because testing measures the quality of the software system and helps to increase the quality

Because testing finds more defects than reviews and inspections.

Black box testing is when we do not have knowledge of testing and in white box testing we have knowledge of testing.

Black box testing is when we do not know the functionality and in white box testing we know the functionality.

Black box testing is when we do not know code used and in white box testing we know the code used.

Black box testing is when we test application randomly and in white box testing we test application using proper test strategy.

Testing that the system functions with other systems

Testing that the components that comprise the system function together

Testing the end to end functionality of the system as a whole

Testing the system performs functions within specified response times

Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

Re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

Re-testing is done after faults are fixed; regression testing is done earlier

Re-testing is done by developers; regression testing is done by independent testers

All the planned tests have been run

Time has run out

All faults have been fixed correctly

Both 1 and 3

It depends on the risks for the system being tested

Parallel testing is a type of testing where the tester reconciles the output of the new system to the output of the current system, in order to verify the new system operates correctly.

Two people testing an application on same machine.

Testing one functionality simultaneously on two different machine having same hardware configuration.

Testing two different functionality simultaneously.

Interoperability (compatibility) testing, reliability testing, performance testing

System testing, performance testing

Load testing, stress testing, component testing, portability testing

Testing various configurations, beta testing, load testing

Number of detected defects, testing cost

Number of residual defects in the test object.

Percentage of completed tasks in the preparation of test environment; test cases prepared

Number of test cases run / not run; test cases passed / failed

State transition testing, code testing, agile testing

Equivalence partitioning, state transition testing, decision table testing

System testing, acceptance testing, equivalence partitioning

System integration testing, system testing, decision table testing