Scribd
Upload
153 views31 pages

Business Process Testing BASIC

Uploaded by

Harivelan Gnanavel
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
153 views31 pages

Business Process Testing BASIC

Uploaded by

Harivelan Gnanavel
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 31

Home

BPT
Business Process Testing
BASIC

Presented
by Ali
-- Naem
Introduction to Business Process Test
BPT Overview

BPT is Released in 2004 with QTP/WR.

Business Process Testing (BPT) allows for non-technical


experts to build tests with out having to understand a
coding language. 

BPT is basically an application layer over QuickTestPro or


Win-Runner, both of which are their legacy
record/playback/scripting tools. 

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. -3-
Features of BPT

Start test case design early in the software development lifecycle.

Automate maintenance of test cases and test plan documentation.

Manage change impact for SAP applications.

Unify distributed tests with test asset reuse.

Detect and diagnose application problems before you go live.

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. -4-
BPT Life Cycle
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

Application Define Business Batch


Functionality Approach Flow for all Execution Customized
Study Business Using Test Reports
Design Components Management
Application Tool(QC) Traceability
Area
Reusable
Evidence User Manual
Identify Components
Capturing
Business
Components Parameterization
Results
Spec Analysis
Static Review
Preparation
Script Dry Run
BPT – Requirement Analysis
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

Understand application under test


Identify the testing tool to be used
Identify scenarios/test cases to be automated
Check automation feasibility of identified scenarios/test cases
Perform a POC on any of the identified scenario/test case

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. -6-
BPT - Design
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

• Prepare automation test strategy


• Define the Application Area

• Identify the business components for the Application Area

• Identify the code conventions and standards for the testing tool

• Prepare component specification

• Prepare component verification


Copyright Polarischecklist
Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. -7-
BPT - Scripting
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

• Common Object Repository Preparation


• Generate common libraries(User-Defined Functions)
• Scripting of Individual Business components
• Synchronize for inherent application delays
• Add verification points
• Plan recovery scenarios
• Integrate, review, run and validate the scripts

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. -8-
BPT - Execution
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

Add the Business Components to the Test Plan in QC

Parameterization is done to run the tests for different sets of Data

Schedule and Run the scripts in uninterrupted mode through Test Lab

Analyze the results

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. -9-
BPT - Reporting
Re-execution on need basis

1 2 3 4 5
Requirement
Analysis Design Scripting Execution Reporting

Generate customized reports on script execution

Generate traceabilty between the scripts executed and scenarios identified

Prepare and publish automation test report

Re-execute the scripts on need basis

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 10 -
Modules in BPT

Business Requirement
Business component
Test Plan
Test Lab
Defect

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 11 -
Business Requirement

Business
Requirement

 Mapping of components with Business Requirements is done by the


SME‘ s (Subject Matter Experts).
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 12 -
Business Components

Details

Business
Components

 Designing of Components according to the Scenarios


 It describes the overall summary of BC with pre and post conditions
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 13 -
Snapshot..

 We can capture snapshot and store in BPT for a particular component

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 14 -
Parameters..

 We can add parameters to Components in Business Component Module


Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 15 -
Creating New Parameters

 Creating New parameter and giving name to it.

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 16 -
keyword View ...

 We can have only Keyword view in BPT


Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 17 -
Components Used By ..

 Here we can we view all the users who are using the component.
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 18 -
Test Plan

Test Plan

 It is like a design phase


 Designing the Scenarios by mapping the components.
 Objects are stored in Application Area in QC
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 19 -
Editing a Component

 We can modify a particular component by using Edit Component option


Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 20 -
Creating Input/Output Parameters to a Component ..

 We can pass the run-time input/output values to components

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 21 -
Creating Input/Output Parameters to a Component ..2

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 22 -
Running the scenario ..

Run Button

 Run the scenario by pressing Run Button


Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 23 -
Ready to run the scenario..

 Dialog window showing that Ready to run all this Scenarios


And diff. Components that are included.
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 24 -
Attachments …

 Uploading the user defined function as an attachments


Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 25 -
Attachments..

 When we select a particular module, It will show all files related that particular module

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 26 -
Attaching the user defined function files

 Designing the Test sets by mapping the Scenarios


 Executing the Scripts according to the Scenarios

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 27 -
Scripts Execution in Execution Grid ..

Test Lab

 We can run the multiple test scenarios as Batch by drag & drop

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 28 -
Running single Batch/All the Batches at once

 Running scenarios, individual Batch/All the Batches at once

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 29 -
Defects..

Defects

 Used for Tacking defects


 Defects which are found while execution are logged here
Copyright Polaris Software Lab Limited, 2005.
Confidential. Not to be republished without prior consent. - 30 -
THANK YOU ….

Copyright Polaris Software Lab Limited, 2005.


Confidential. Not to be republished without prior consent. - 31 -

You might also like