Quizlet

2.2 Test levels (K2)

Share this set

About this set

Created by:

michelle-1962  on June 9, 2010

Subjects:

ISTQB, Testing, Testing Methods

Description:

Terms Alpha testing, beta testing, component testing (also known as unit, module or program testing), driver, field testing, functional requirement, integration, integration testing, non-functional requirement, robustness testing, stub, system testing, test level, test-driven development, test envirTerms

Alpha testing, beta testing, component testing (also known as unit, module or program testing),

driver, field testing, functional requirement, integration, integration testing, non-functional

requirement, robustness testing, stub, system testing, test level, test-driven development, test

environment, user acceptance testing.

Background

For each of the test levels, the following can be identified: their generic objectives, the work

product(s) being referenced for deriving test cases (i.e. the test basis), the test object (i.e. what is

being tested), typical defects and failures to be found, test harness requirements and tool support,

and specific approaches and responsibilities.
Per ISTQB FOundation course 2007. (see more)

Log in to favorite or report as inappropriate.
Pop out

Discuss

No Messages

You must log in to discuss this set.

2.2 Test levels (K2)

Component testing (K2)
Component testing searches for defects in, and verifies the functioning of, software (e.g. modules,
programs, objects, classes, etc.) that are separately testable. It may be done in isolation from the rest of the system, depending on the context of the development life cycle and the system. Stubs, drivers and simulators may be used.

Typically, component testing occurs with access to the code being tested and with the support of
the development environment, such as a unit test framework or debugging tool, and, in practice,
usually involves the programmer who wrote the code. Defects are typically fixed as soon as they
are found, without formally recording incidents.
1/2

Study:

Cards (new!)

Learn

Test

Speller

Scatter

Games:

Scatter

Space Race

Tools:

Export

Copy

Combine

Embed

Order by

2 terms

Terms

Definitions

Component testing (K2)Component testing searches for defects in, and verifies the functioning of, software (e.g. modules,
programs, objects, classes, etc.) that are separately testable. It may be done in isolation from the rest of the system, depending on the context of the development life cycle and the system. Stubs, drivers and simulators may be used.

Typically, component testing occurs with access to the code being tested and with the support of
the development environment, such as a unit test framework or debugging tool, and, in practice,
usually involves the programmer who wrote the code. Defects are typically fixed as soon as they
are found, without formally recording incidents.
Integration testing (K2)Integration testing tests interfaces between components, interactions with different parts of a system, such as the operating system, file system, hardware, or interfaces between systems.

1. Component integration testing tests the interactions between software components and is done
after component testing;
2. System integration testing tests the interactions between different systems and may be done
after system testing.

First Time Here?

Welcome to Quizlet, a fun, free place to study. Try these flashcards, find others to study, or make your own.

Set Champions

There are no high scores or champions for this set yet. You can sign up or log in to be the first!