Business Process Testing Icons

This section describes the icons available for Business Process Testing in the Business Components module, Test Plan module, and Test Lab module.

Option	Description
To access	On the sidebar, under Testing, select Business Components, Test Plan, or Test Lab.
Important information	The status of a business component affects the status of any business process tests or flows of which it is a part. The component with the most severe status determines the status of the test or flow. For example, a business component with an Error status causes any business process test or flow of which it is a part to have an Error status. Additional statuses can be defined by updating the project list for business component statuses. For details, see Customize field lists.
See also	Business Components Module Menus and Buttons Business Components Module Window

Option

Description

To access

On the sidebar, under Testing, select Business Components, Test Plan, or Test Lab.

Important information

The status of a business component affects the status of any business process tests or flows of which it is a part. The component with the most severe status determines the status of the test or flow. For example, a business component with an Error status causes any business process test or flow of which it is a part to have an Error status.
Additional statuses can be defined by updating the project list for business component statuses. For details, see Customize field lists.

See also

The icons are described below:

UI Element	Description
	<green asterisk>. The applicable tab is populated.
	Automated. A business component that has been automated using a testing tool such as OpenText Functional Testing.
	A business component that does not have a manual implementation or automation.
	Error. The red symbol indicates that the business component contains errors that need to be fixed, for example, due to a change in the application. When a business process test or flow contains a component with this status, the status of the entire business process test or flow is also Error.
	Learned. BPT Packaged Apps Kit created the business component using the Learn process.
	Maintenance. The yellow triangle indicates that this business component was previously implemented and is now being modified.
	Manual. A manual business component.
<no icon>	Not Implemented. Indicates that a manual business component has been requested in the Test Plan module. The component request status changes from Not Implemented to Under Development when you move the request from the Component Requests folder in the component tree. Note: This status is available from the Test Plan module.
	Obsolete. The component is obsolete, cannot be modified, and should not be used in business process tests or flows.
	Ready. For components: A green-circled checkmark indicates that this business component is fully implemented and ready to be run. For business process tests and flows: A green checkmark indicates that a business process test or flow is ready, meaning, all its components are ready.
	Under Development. The yellow triangle indicates that this business component is currently under development. This status is assigned to: New components Component requests dragged or moved out of the Component Requests folder into a component folder
	Comment. The information on the current row in the automated component's Keyword View is a comment. Available from: OpenText Functional Testing Keyword View in the Automation tab
	Missing Object. The automated component contains an object that is missing from the shared object repository. Available from: OpenText Functional TestingKeyword View in the Automation tab
	Constant. The automated component contains an output value configured as a constant. Available from: OpenText Functional Testing Keyword View in the Automation tab
	Component Parameter. The automated component contains an output value configured as a component parameter. Available from: OpenText Functional Testing Keyword View in the Automation tab
	Local Parameter. The automated component contains an output value configured as a local parameter. Available from: OpenText Functional Testing Keyword View in the Automation tab
	Version Control. The component is checked out. Green lock. The component is checked out by the current user. Red lock. The component is checked out by another user. For details on working with version control in OpenText Application Quality Management, see Version control.