Share this page

# Test Plan Module Window for Business Process Testing

This version of the Test Plan module window enables you to define and maintain business process tests and flows.

To access | On the ALM sidebar, under Testing, select Test Plan. Select a business process test or flow in the test plan tree.
Important information | The Test Plan module for Business Process Testing differs from the Test Plan module for other ALM test types. This section describes the elements that are significant specifically when designing business process tests and flows. For user interface details on the Test Plan module for other test types, see the Micro Focus Application Lifecycle Management User Guide: Test Plan Module Window.
Relevant tasks | How to Plan Business Process Tests and Flows How to Create Business Process Tests and Flows
See also | Business Process Test and Flow Specification Overview Test Plan Module Fields for Business Process Testing Micro Focus Application Lifecycle Management User Guide : Test Plan Module Window

User interface elements unique to Business Process Testing are described below (unlabeled elements are shown in angle brackets):

UI Element (A - Z) | Description
--- | ---
<Test Plan for Business Process Testing module common UI elements> | Test Plan for Business Process Testing fields. For field definitions, see Test Plan Module Fields for Business Process Testing. Test Plan for Business Process Testing menus and buttons. For command and button descriptions, see Test Plan Module Menu and Buttons for Business Process Testing. Test Plan for Business Process Testing icons. For icon descriptions, see Test Plan Module Icons for Business Process Testing.
<Test plan tree> | Organizes and displays your tests hierarchically. Note: In previous versions of ALM and Quality Center, the BPT Resources folder was created in the Test Plan module. For business process tests or flows to perform properly in ALM, this folder and its subfolders should not be renamed or deleted. In ALM, the BPT Resources folder no longer exists in the Test Plan module. This folder, which contains the business component resources in the project, is created automatically in the Test Resources module the first time you click the Automation tab in a new project, when you create a UFT automated component for the first time, or when UFT connects to ALM for the first time.
Criteria | Enables you to view the entities, such as flows and business components, that comprise a test. These entities are defined as criteria, and are used for the purposes of analyzing requirement coverage at a more granular level. For task details, see How to Create Coverage by Criteria.
Details | Lists the business process test or flow fields. For details on fields specifically for Business Process Testing, see Test Plan Module Fields for Business Process Testing. For details on other test fields, see the Micro Focus Application Lifecycle Management User Guide: Test Plan Module Fields.
Parameters | Lists parameters associated with the currently selected test or flow. Enables you to define parameters at the test and flow level. Parameters can be incorporated in the test's or flow's components' steps. For task details, see How to Handle Data in Business Process Testing.
Test Configurations | Enables you to define and update test configurations. For details specific to Business Process Testing, see Business Process Test Configurations Overview. For task details, see the Micro Focus Application Lifecycle Management User Guide: How to Work with Test Configurations.
Test Script | Enables you to build the structure of the business process test or flow by adding business components (and, in the case of tests, flows). For details, see Test Script Tab for Business Process Testing.

https://admhelp.microfocus.com ALM 8942
Tips to improve your search results... ALM Help Center ALM Help Center ALM Help 15.5-15.5.1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: