Tag: testing

tests the individual components that have been developed.

tests interactions between modules or subsystems

only uses components that form part of the live system.

tests interfaces to other systems.

updating tests when the software has changed

testing a released system that has been changed

testing by users to ensure that the system meets a business need

testing to maintain business advantage

) It is easier to manage testing in stages

We can run different tests in different environments

Each test stage has a different purpose.

The more stages we have, the better the testing.

can only be used in component, integration and system testing.

supplements formal test design techniques.

is only performed in user acceptance testing.

is not repeatable and should not be used.

time runs out.

no more faults are found.

the users won’t find any serious faults.

the required level of confidence has been achieved.

Usability testing

Performance testing

Boundary value analysis

Security testing

the analysis of batch programs.

the analysis of program code

the reviewing of test plans.

the use of black box testing

performed by an Independent Test Team

performed by customers at the software developer’s site

performed by customers at their own site

performed as early as possible in the lifecycle

Poor quality software

bad luck

Poor software and poor testing

insufficient time for testing

Coverage analysis

Dynamic analysis

State analysis

Memory analysis