<< Glossary - functional test | Index - ActiveX Type Library >>

Glossary - sequence diagram

145

sequence diagram.

A graphical view of a scenario that shows object interaction in a

time-based sequence--that is, what happens first, what happens next. Sequence diagrams
establish the roles of objects and help provide essential information to determine class
responsibilities and interfaces. This type of diagram is best used during early analysis phases
in design because they are simple and easy to comprehend. Sequence diagrams are normally
associated with use cases. Sequence diagrams are closely related to collaboration diagrams
and both types of diagrams are alternate representations of an interaction. There are two main
differences between sequence and collaboration diagrams: sequence diagrams show
time-based object interaction while collaboration diagrams show how objects associate with
one another.

session bean.

A session bean typically models business concepts that can be expressed as a

verb, such as managing an account or executing a transaction. A session bean is created by a
client and in most cases exists only for the duration of a single client/server session. Session
beans can be transactional, but (normally) they are not recoverable following a system crash.
Session beans can be stateless or stateful.

stub.

The minimum set of interfaces for a component that interacts with the

component-under-test. Stubs can be used to control the results returned from components that
are dependent on the component-under-test.

test case.

A set of test inputs, execution conditions, and expected results developed for a

particular objective, such as to exercise a particular program path or to verify compliance with
a specific requirement.

test script.

Test scripts are the computer-readable instructions that automate the execution of

a test procedure. Test scripts can be generated automatically using test automation tools,
programmed using a programming language, or can result from a combination of recording,
generating, and programming. With Rational test generation tools, the test script also includes
a repository object. EJB test scripts, in particular, are generated in Java, and all generated Java
test scripts extend the TestScript class.

test log.

See log.

TestManager.

See Rational TestManager.

verification point.

A functional testing construct used by a test script to verify a specific

behavior of the application or component-under-test. Static verification points capture
information about the application-under-test and store it as the baseline. During playback, a
verification point recaptures the object information and compares it to the baseline. Results of
the verification point are maintained in a log, allowing for analysis of overall functional
correctness and test case coverage.

white-box testing.

Tests that rely on knowledge of the code, specifications, or other source

material to perform the test. White-box testing is also called Structural testing. Rational
QualityArchitect is an example of a white-box testing tool.