Search This Blog

Showing posts with label BPT. Show all posts
Showing posts with label BPT. Show all posts

Monday, September 28, 2009

Overview of BPT in QC

Business Components module:
Location where components are stored.
Test Plan module:
Location where test scripts are created and stored.
Location where Components are requested.
Test Lab module:
Location where test scripts are executed.

Requesting Components:
Create a new test in QC’s Test Plan module.
Navigate to the “Test Script” tab.
Click the “New Component request” button.
Fill in the new component request form.
Wait for Component status to become “Ready”.

Who will be using BPT?

Groups of BPT Users:
1.Subject Matter Experts (SME)
2.Automation Experts

Subject Matter Experts (SME):This is defined as a tester who is very knowledgeable with the AUT and capable of writing highly detailed manual test cases.
The Role of the SME is to:
Write exact test steps required for the component to playback and verify steps (must include data to use).
Request for Components to be automated.
Create the BPT test script. This will be done by adding components to the test script.
Execute BPT test scripts.
Gather test results.

Automation Expert:This is the person who will be using QTP to automate Components.
The Role of the Automation Expert:
Convert Manual Components into Automated Components.
Update and Maintain Automated Components.

When Should Components Not be Created?

One time testing.
Need to test ASAP.
Steps will not be reused *.
Expected results are not predictable.
AUT’s objects/business rules keep changing.
Cosmetic verifications (color, font…)

When Should Components be Created?

When steps will be repeated - even if the data is different for each iteration. The more repeatable, the better.
When the AUT is stable.

What is BPT - Business Process Testing?

Business Process Testing (BPT) is Mercury’s tool and concept which allows inexperienced automaters to easily create automation test scripts by piecing together reusable business components.
Components are a group of test steps that can be used in multiple test cases as well as in the same test case.
Components are seen in QC as icons (that look like pieces from a jig saw puzzle) but they contain QTP code.
In general, each screen/page in the AUT (Application Under Test) will have just one component created for it.