Business Process Testing
Terms
|
Definitions
|
Application
area
|
Application
areas contain all of the settings and resources required to create the
content of keyword-driven business components for a particular application or
part of an application. These include representations of the objects from
your application contained in the shared object repository, and user-defined
operations, contained in function libraries.
|
Automation
Engineer
|
An
expert in a HP Quick Test Professional.
|
Business
Component (or Component)
|
An
easily-maintained, reusable unit comprising one or more steps that perform a
specific task. A business component can be defined as a manual or automated
component. Business components may require input values from an external
source or from other components, and they can return output values to other
components.
|
Business
Process Test
|
A
scenario comprising a serial flow of business components, designed to test a
specific business process of an application.
|
Business
Process Test Run-Time Parameters
|
Variable
values that a business process test can receive and then pass to business
components for use as input component values.
|
Business
Process Test Status
|
The
user who uses Quality Control to create business components and business
process tests.
|
Test
Plan Module
|
A
status value that is automatically generated based on the status values of
all the business components in a business process test.
|
Component
Input Parameters
|
Variable
values that a business component can receive and use as the values for
specific, parameterized steps in the component.
|
Component
Output Parameters
|
Values
that a business component can return. These values can be viewed in the
business process test results and can also be used as input for a component
that is used later in the test.
|
Component
Request
|
A
request for the creation of a new business component, when no existing
component answers the needs of a business process test.
|
Component
Status
|
A
status value that indicates whether a business component is fully
implemented, debugged, and ready to be run in a business process test. The
component with the most severe status in a test determines the status of the
entire test. The status can be modified by the Subject Matter Expert in
|
Implementation
requirements
|
Details
and information, written by the Subject Matter Expert that creates a business
component, describing a general overview of the business component’s purpose
or goals, and the condition of the application before and after a component
is run (the preconditions and post-conditions).
|
Iterations
|
The
number of times that an individual business component, or group of
components, runs within a single test run, or the number of times that an
entire business process test runs within a test set.
|
Pre-Condition
and Post-Condition
|
The
state of the application before the first step in a business component, and
the state of the application after the last step in a business component. For
example, the pre-condition for a component may state that all applications
should be closed, or a specific application should be open to a specific
screen or with a specific dialog box displayed. A post-condition may state
that an application should be open to a particular screen, or be closed.
|
Roles
|
The
various types of users who are involved in Business Process Testing.
|
Steps
|
Individual
operations in a component. These can be manual steps or detailed automated
testing steps and are designed and implemented in a business component to
test the workings of a specific task in an application.
|
Subject
Matter Expert
|
The
subject matter expert who uses
|
For Online Class contact:
No comments:
Post a Comment