Tag: testing

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.