Tag: testing

When the specified number of faults are found.

When the test completion criteria are met.

When all high and medium priority tests are complete.

When all statements have been executed.

Estimating test duration.

Incident Management.

Configuration Management.

De-bugging.

Metrics from previous similar projects.

Discussions with the development team.

Time allocated for regression testing.

Both A & B.

Compiling code is not a form of static analysis.

Static analysis need not be performed before imperative code is executed.

Static analysis can find faults that are hard to find with

Extensive statistic analysis will not be needed if white- Box testing is to be performed.

Testing whether a known software fault been fixed.

Executing a large number of different tests.

Testing whether modifications have introduced adverse side effects.

Using a test automation tool.

This is an acceptable risk of a multi-user system.

Insufficient functional testing has been performed.

This indicates an important non-functional requirement was not specified and tested.

It is not possible to test against such events prior to release.

Testing the system when combined with other systems.

Testing a sub-system using stubs and drivers.

Testing a system with a large number of users.

Combing software components and testing them in one go.

How rapidly data is transferred through a program.

The rate of change of data values as a program executes.

The use of data on paths through the code.

The intrinsic complexity of the code.