How to Create and Execute The Business process Tests

 Business Process Testing Framework creation and Execution in detail:

Hi Readers...! previously I given idea about Business Process Testing ! now I want to give some boost to continue the Business Process Testing  .
In this Post am explaining about the complete picture of Business Process Testing  process means what is the Role of QTP & QC in Business Process Testing ,what Modules we supposed to create Business Components and Execute Business Components by Automation Approach 

Take a look down to  Business process Testing Framework in detailed

we can broadly categorized the approach of BPT into three levels 

and Roles who are Responsible to complete of their part in BPT .Here In Automation  process only two roles are presented one is Subject Matter Expert and second one is Automation Tester .this depends on companies .but sometime Automation Tester only will do both work.

The top-down methodology presented here for working with Business Process Testing comprises:

1.Design low level components :(identify the components)

Role: done by the SME

The top-down methodology presented here for working with Business Process Testing comprises 

2. High level design : Create structure for Business Process Tests
Role: done by both Subject Matter Expert (SME) and Automation Test Engineers (ATE)

3. The mid-level design
-- Creation of flows (sets of business components in a logical order that can be executed).
-- Creation of business components (reusable units that perform specific tasks in a business process).
--Specifying criteria for more granular test coverage (requirements) as necessary.
 --Specifying different test configurations for testing different use-cases and for more "true-to-life" test coverage (requirements).
Role: done by the SME

4.The low-level design :

The low-level implementation of business component content by creating component steps, setting up iterations (for business process tests, flows, and components), parameter zing  and when necessary,

Automating.

Role: The SME, the Automation Engineer, or both together, depend on available skills and resources.

The Execution of the business process tests:

The Business Process Tests contains >> business component flows or business components >>

Business components Contains steps

Test Plan Module :

     1. The SME first creates a business process test or flow in the Test Plan module. (Flow is a collection of business components in a fixed sequence that can be used as a unit in multiple business process tests. Flows Are available only in HP ALM / Quality Center.)

-- To populate the business process test or flow, the Subject Matter Expert then selects (drags and drops) the relevant components and configures their run settings.

2.  Each component can be used differently by different business process test configurations or flows.  For example, for each test configuration, the component can use different input parameter values or run a different number of iterations.

Business Components Module:

1.  Before automated testing resources are available, SME can define manual steps using the Business Components module. They can add these manual components to a business process test and run the steps manually using the HP ALM / Quality Center Manual Runner.

2. SME can add comments in the Business Components module. This enables them to enter any additional information or remarks that they want to communicate to you, the Automation Engineer, such as requests for new operations, future changes planned for the component, or alternative tests in which the component can be used.

3. Create individual Application Areas (Means A collection of resources and settings that are used for the creation and implementation of business components) for the various parts of your application based on real testing needs.

4. After creating the Application Areas and define its settings and resource files, the SME can incorporate these automated testing resources in business component steps, convert any existing manual components to automated components, and create new automated components.

Take a Look on the below image to understand the concepts

key elements in image :

1. Details: Provides a general summary of the component’s purpose or goals, and the condition of the application before and after a component is run (its pre-conditions and post-conditions). You can specify details and implementation requirements for the currently selected business component.

 2. Snapshot: Displays an image that provides a visual cue or description of the component’s purpose or operations. You can capture a snapshot image from the application and attach it to the currently selected business component.

3. Component Steps: Enables you to create or view the manual steps of your business component, and to automate it if required.

4. Parameters: Specifies the input and output component parameters and parameter values for the business component. This allows the component to receive data from an external source and to pass data to other components or flows.

5. Dependencies tab: displays a list of assets that are linked to the currently selected business component, enabling you to view the dependency relationships between components, tests, flows, and resources (including application areas).

6. History tab: Displays a log of changes made to the component.

7. Live Analysis tab: When a folder is selected, this tab is available for creating a graphical representation of data related to business components.