VIP - Leveraging HP Business Process Testing

Views:
 
Category: Entertainment
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

HP Business Process Testing: 

HP Business Process Testing Leveraging HP Business Process Testing to Utilize Multiple Data Sources for Data-Driven Tests

Topics to be Covered: 

2 of 48 Topics to be Covered Overview - Business Process Testing Review Existing Database Driven Test Suite Business Case for Upgrading to BPT/QTP Building the New BPT/QTP Solution Add BPT Data-Driving Component Lessons Learned

PowerPoint Presentation: 

3 of 48 Overview - Business Process Testing

Grocery Store Analogy for BPT: 

Grocery Store Analogy for BPT Grocery Store is made up of components: Entrance Check Out Meats/Deli Exit Dry Goods Dairy Bakery Produce Frozen Foods Some components must be processed in a specific order: Entrance Check Out Exit 4 of 48

Business Process Testing Overview: 

5 of 48 Business Process Testing Overview BPT is an Add-In Module for Quality Center Reusable BPT Components Components Can be Manual, WinRunner, QuickTest Professional Modular (Self Contained) Log in, Input Data, Log out Input and/or Output Parameters Drag-and-drop into BPT Test Cases

Grocery Store Components: 

Grocery Store Components Inputs for Dairy (What do we want from Dairy) Milk Butter Yogurt Flavor Size Outputs from Dairy (What did we get from Dairy) Cost Out of Stock? Items & Activities are Specific to Each Component Inputs Outputs 6 of 48

Business Process Testing Overview: 

7 of 48 Business Process Testing Overview BPT Components: Input Parameters Data Consumed by Component Provided by Quality Center Users Output Parameters from Another Component Output Parameters Derived in the Component Script Pass Through (Set Output Parameter = Input Parameter) Inputs Outputs

Business Process Testing Overview: 

Business Process Testing Overview Input Parameters Output Parameters BPT Component 8 of 48

Grocery Store “Template”: 

Grocery Store “Template” Store Components Assembled in a “Template” of the Store Layout 9 of 48

Determine Shopping Path: 

Determine Shopping Path Shopping Path Entrance Produce Meats & Deli Frozen Foods Dairy Dry Goods Bakery Check Out Exit 10 of 48

Reuse “Components” : 

Reuse “Components” Different Shopping Path Entrance Produce Dry Goods Frozen Foods Dairy Dry Goods (Again) Check Out Exit 11 of 48

Business Process Testing Overview: 

12 of 48 Quality Center BPT Tab Test Case Tab Business Process Testing Overview Login Input Data Retrieve Report Logout Login Input Data Logout Login Retrieve Report Logout Assemble BPT Components into Test Cases Add Test Cases to Test Sets Build BPT Components

PowerPoint Presentation: 

13 of 48 Case Study: Review Existing Database Driven Test Suite

Previous Version of AUT: 

14 of 48 Previous Version of AUT HTML Based User Interface 3 Pages 1 End-Point for all Business Scenarios Existing Application Under Test: Page 1 Decision Engine Page 2 Page 3

WinRunner for Previous AUT: 

15 of 48 Quality Center WinRunner for Previous AUT 350 Tests to Support UAT Manual Effort = 7 weeks Automation w/ WinRunner = 8 hours Test Data Stored in MS Access Database WinRunner Automation Framework Access Driving Scripts Application Under Test Test Data & Expected Results for 350 Regression Tests

PowerPoint Presentation: 

16 of 48 Business Case for Upgrading to BPT/QTP

Business Case - Requirements: 

17 of 48 Business Case - Requirements Application Redesigned in ASP.NET HTML Pages Changed to UI Tabs 1 Business Flow Changed to 9 Flows Keep Existing Regression Tests Quickly Test Flexible Logical Flows Use Automation, but Non-Technical Testers Ensure Ease of Test Suite Maintenance as Application Evolves

AUT Redesigned: 

18 of 48 AUT Redesigned New Application Under Test : New ASP.NET User Interface 12 Tabs – Red Denotes Possible Business Scenario End-Points Tab 6b Decision Engine Tab 7b Tab 8a Tab 7a Tab 6a Tab 5b Tab 5a Tab 4 Tab 3 Tab 2 Tab 1b Tab 1a

Business Case – Solution: 

Business Case – Solution WinRunner is Not Compatible with ASP.NET. QTP Is ! BPT is Modular like New AUT UI Architecture BPT Can Leverage QTP Automation BPT/QTP Can Be Integrated with Existing MS Access Database BPT Components Easy to Assemble into Test Cases BPT Components Simple to Maintain 19 of 48

PowerPoint Presentation: 

20 of 48 Building the New BPT/QTP Solution

New Solution Walk-Through: 

21 of 48 New Solution Walk-Through Create Components in Quality Center BPT Tab Create Initialization Component Create One Component for Each Tab Create Verification Components Create QTP Automation for New BPT Components Drag and Drop Component(s) into Test Case Templates

Create BPT Components: 

22 of 48 Create BPT Components Tab 6b Decision Engine Tab 7b Tab 8a Tab 7a Tab 6a Tab 5b Tab 5a Tab 4 Tab 3 Tab 2 Tab 1b Tab 1a Created Init Component Added One BPT Component per Tab Verified with 9 Additional BPT Components Initialization Component:

Example New AUT BPT Component: 

23 of 48 Example New AUT BPT Component 7 Input Parameters 0 Output Parameters BPT Component

QTP Code for BPT Component: 

24 of 48 QTP Code for BPT Component

Create Test Case: 

25 of 48 Create Test Case Steps to Create BPT Test Case: Create New Test Case Select Test Type = Business Process Drag & Drop Components to “Assemble” Test Case Link Parameters Between Components

Drag & Drop BPT Components: 

26 of 48 Drag & Drop BPT Components Click on Input Value

User Input Data: 

27 of 48 User Input Data

Repeat For Each BPT Component: 

28 of 48 Repeat For Each BPT Component

PowerPoint Presentation: 

29 of 48 Add BPT Data-Driving Component

Add BPT Data-Driving Component: 

30 of 48 Add BPT Data-Driving Component Solution: Use Data-Driving Component Leverage Existing Access Database Leverage New BPT Components Application Under Test Tab 1 Decision Engine Tab 2 Tab 3 BPT BPT BPT Access Data-Driver 350 BPT Test Cases

Database Driven BPT Component: 

31 of 48 Database Driven BPT Component Create Open Data Base Connection (ODBC) Create BPT Component Create QTP Script Add to “Template” Test Case Connect Data-Driver Output Parameters to Other BPT Component Input Parameters

Create ODBC connection: 

32 of 48 Create ODBC connection Select Administrative Tools from Control Panel Select Data Sources (ODBC)

Create ODBC Connection: 

Create ODBC Connection 33 of 48 Click Add Button Select MS Access Type Data Source Name Select Database Click OK Note - New ODBC Created Click OK to Close Dialog Box

Create BPT Component: 

34 of 48 Create BPT Component 1 Input: Test Name 51 Outputs: One to One Correlation with MS Access Database Columns

Create QTP Script – Get Data: 

Create QTP Script – Get Data Query Data from MS Access 35 of 48 Establish Connection to MS Access Build SQL Query, Element by Element

Create QTP Script –Link Data: 

36 of 48 Create QTP Script –Link Data Link Query Response to Output Parameters Clean Up ODBC Connection Objects

Update “Template” with Data-Driver: 

37 of 48 Update “Template” with Data-Driver

Select BPT Component to Modify: 

38 of 48 Select BPT Component to Modify Click the Input Parameters to Open Dialog Box

Link Data-Driver Data to BPT Component: 

39 of 48 Link Data-Driver Data to BPT Component Select the “Output of previous component” Checkbox

Link Data-Driver Data to BPT Component: 

40 of 48 Link Data-Driver Data to BPT Component Select the Correct Parameter

Connect Data-Driver to Modular Components: 

41 of 48 Connect Data-Driver to Modular Components Repeat for All Applicable Parameters

Data-Driver Complete: 

42 of 48 Data-Driver Complete Done! Copy and Paste the “Template” as Many Times as Needed Change “Test Name” Input Parameter on the Data-Driver Component to Retrieve Different Test Case.

PowerPoint Presentation: 

43 of 48 Lessons Learned

Two Implementations: 

44 of 48 Two Implementations Regression Testing 1 Test Case Template 350 Test Cases from MS Access User Configured Tests 9 Test Case Templates 20 “Classic” BPT Test Cases More Added With Each Release

Test Execution Setup Options: 

45 of 48 Test Execution Setup Options One Test Case, Many Iterations Easy to Manage / Change Single Host Execution Less Detailed Quality Center Reporting Many Test Cases, One Iteration Difficult to Manage / Change Multiple Host Execution Granular Quality Center Reporting

“Classic” BPT vs. External Database: 

46 of 48 “Classic” BPT vs. External Database Test Data Managed in “Classic” BPT Each Classic BPT Test Cases must be Updated Individually No Good Way to Reporting on Test Case Data Test Data Stored in External DB Finding and Managing Test Data is as Simple as Querying MS Access Reporting On Test Case Data is Also Simple

Summary: 

47 of 48 Summary Reviewed Business Process Testing Discussed Existing Database Driven Test Suite Explained Business Case for Upgrading to BPT/QTP Described Building the New BPT/QTP Solution Demonstrated How to Add BPT Data-Driving Component Discussed Lessons Learned

PowerPoint Presentation: 

48 of 48 Questions ?