HP’s Business Process Testing (BPT) in a Nutshell

I was asked to give a Business Process Testing demo this week.

To prepare, I created some simple graphs and a video that I thought might be helpful for visualizing some core BPT concepts.

I believe that sometimes a graphic or video is the most effective way of conveying an abstract idea. Here are the graphs I created, along with a high-level outline of what each graph represents. I hope you find them helpful.

Is BPT separate from QTP?

One of the questions I’m asked most often when giving a demo for BPT is: “Is BPT a different functional tool then QTP?” The answer is, not really. I think of BPT as an extra layer that wraps around QTP and uses QC as a user-friendly interface for test automation creation that, in theory, is meant to make testing easier for non-technical users.

What is a BPT made of?

The two main elements that make up a BPT are not much different than a QTP test:

  • Object Repositories

The first step in creating business components is the same step you would begin with for QTP — that is, to create an Object Repository — exactly like you would with QTP.

  • Function Libraries

After you have your OR setup, you would normally create a function library which contains common functionalities that are frequently used against your application.

What’s new to BPT is the concept of an Application Area.

What is an Application Area?

So — once you have your test resource setup (like your OR and function library), the next step is to bundle all the resources into an application area. The application area provides a single point of maintenance for all elements associated with the testing of a specific part of your application. Typically, you should define separate application areas for each portion of your application and associate a component with the appropriate application area.

BPT Components

Business components are the reusable, easy-to-maintain building blocks of a business process test — kind of like Legos. These components are usually made up of one or more steps that perform a specific task in your application.

Building a Business Process Test 

Once your components are created, A Quality Center business user who is using a QC visual interface can create a test. The components can be by strung together by dragging and dropping them into QC’s test plan test area. Once they’re in the test plan, each components test data is exposed and easily changed.

BPT Getting Started Video

BPT Overview In this video, I cover HP’s Business Process Testing. Business Process Testing, also know as BPT, is comprised of a number of components, and these components are the building blocks of a test. Components are reusable actions or modules that perform a specific task(s) in an application.

BPT Example

In my application, I have actions like login, logout, new appointment, and a new registration. All of these would be considered “components.”
A new business process test would involve taking these components and stringing them together to create the functionality needed for a test.
All this is done within Quality Center.

Build once use many times

Due to their reusability, the same components can be used in multiple business process tests.

BPT In a nutshell

In a nutshell, BPT is just a fancy UI wrapper for QTP that makes it easy for non-technical people to work with automated tests within Quality Center without having any particular knowledge of QTP or coding.

Alan Hatcher - June 27, 2011

I’d suggest replacing “create” with the term “work with” in your last paragraph for this post. The new model that HP uses is the QA Analyst creating tests with components, but an Automation Engineer creates the Automated Components for them.

    Joe Colantonio - June 27, 2011

    Alan Hatcher » Hi Alan – good point! I made the change – thanks.

sharmila - April 4, 2013

What is biggest advantage in using BPT tests rather than QTP tests. I mean here the QTP tests that are created using functions and not using Descriptive programming or recording objects.

    Joe Colantonio - April 4, 2013

    sharmila » Re-usability is probably the biggest benefit. You basically are created reusable building blocks of functionality that can be combined to create numerous test flows.

Joe - August 25, 2016

So how to leverage BPT and LeanFT? Is there a way to define a component that is a LeanFT one or are they 2 different architectures/paradigm and just don’t mix?


Sundaram - February 21, 2017

You are saying that BPT is a fancy UI wrapper for QTP. But I feel slightly different but I could be wrong. I have seen demos where they use BPT just to form a test case by choosing from the different components as required, and then do the tests manually, and clicking the green arrow so that the control goes to the next component and they again test the next step manually and so on. No automation or QTP is used.

So I think BPT can exist even without QTP. As I said, I am very new to this and I could be wrong. Would be great if someone could correct me or reconfirm what I think.
Thanks !

Click here to add a comment

Leave a comment: