All about Business Process Testing (BPT)


I shall share my experience here that might help folks who are planning to adopt BPT :

HP Business Process Testing in a nut shell is used for designing business components that can be reused in business process tests.

Pre- requisite : A separate add-in which comes along with Quality Centre.
QC 10 - [http://update.external.hp.com/qualitycenter/qc100/mictools/qtp/qtp_10/QuickTest_Add-in_for_Quality_Center.msi]

Terminologies:
Components are easily-maintained, reusable units that perform a specific task. Quick Test provides two types of components: Manual / QTP / Winrunner
QTP - business components and scripted components
Business Components are keyword driven components
Scripted Components are regular code driven components.

Application Area: Collection of testing resources  like function libraries, shared object repositories, keywords, testing preferences and recovery scenarios

Component Input and Output Parameters - Variable values to and from a business component.

1. Creating Application Areas
Create, populate, and maintain shared object repository files that are used by Quick Test to identify the objects in your application
Create function libraries that contain functions, or operations/keywords that can be called by a component.
You can create multiple application areas , each one focusing on a particular part of the application.

2. Creating Components in the Quality Center Business Components Module
Details: pre-conditions and post-conditions
Snapshot:  If needed
Parameters: Specifies the input and output component parameter values for the business component. Design Steps: Create or view the manual steps of your business component
Automation:  Create keyword driven components and scripted components
Used by:  Business process tests that include the currently selected business component.
Component Requests pane: Handle new component requests that were generated in the Test Plan module.

3. Creating Business Process Tests and Flows in the Quality Center Test Plan Module SME creates a business process test or flow in the Test Plan module by dragging and dropping required components.

4. Run the BPT tests like regular tests from test lab



Advantages of Business Process Testing Framework:

  1. Eliminates the need of creating a separate framework for the Automation.
  2. Both input and output parameters can be directly added in Quality Centre
  3. A manual tester can remove the unwanted component from the test flow without affecting the code
  4. Single point of maintenance for all elements associated with the testing of a specific part of your application
  5. High reusability with data-driven test components
  6. Quickly test multiple flows , suitable for agile frameworks
  7. Need not have expertise in automation to create and run tests once the components are built
Practical way of applying BPT to your project:
  1. Create components from QC using scripted components
  2. Create atleast one initialization / driver component
  3. Create one component for each reusable functionality
  4. Create Verification components
  5. Create new tests by choosing test type = business component
  6. Drag and drop components into test case templates under test plan
  7. Link parameters between components
  8. Add the tests to test sets in test lab

Update: With QC 10 being really slow wrt BPT HP came up with ALM(Application Lifecycle Managemet) for QC11
In QC 10 every single component that is in a BPT test has to be downloaded separately and run
In QC 11 there is a "BPTWrapperTest" that takes a BPT test, downloads all its components, and generates a single QTP - BPT Wrapper test to run

Comments

Post a Comment

Popular posts from this blog

Software Testing @ Microsoft

Image
In continuation from my previous  series of posts  targeting testing in top few companies from the technology space. After  Software Testing @Facebook  and @Google  we shall now look at Microsoft: Testing@Microsoft Software Development Engineers in Test (SDETs) are usually just called Test and sometimes Software Testing. SDETs are responsible for maintaining high testing and qualityassurance standards for all Microsoft products. Software Development Engineers (SDEs) are often referred to as Software Development. SDEs write the code that drives Microsoft products and upgrades. Very few teams in Microsoft are still using SDETs to do significant amount of manual testing. Manual testing is mainly outsourced. Actually, as early as in 2004, for example, most of the manual testing of MSN Explorer was outsourced. Think about it this way: it just doesn't make sense for test manager to spend their headcount (SDETs) on something can be easily outsourced.  Until 2005, Microso
Read more

Trim / Remove spaces in Xpath?

Image
If you are wondering how you can trim the spaces in your xpath, this is how: The normalize-space function strips leading and trailing white-space from a string, replaces sequences of white-space characters by a single space, and returns the resulting string. Example : Which one is better? //td[starts-with(normalize-space(),'Text to Trim')] //td[starts-with(normalize-space(text()),' Text to Trim ')] The second option is better as it targets at the specific nodes More string functions in XPATH: Functions Description starts-with( string1 ,  string2 ) Returns true if the first string starts with the second string. contains( string1 ,  string2 ) Returns true if the first string contains the second string. substring( string offset length ) Returns a section of the string. The section starts at  offset (which is a number), and is as long as the value provided at  length. substring-before( string1 ,  string2 ) Returns the part of  string1  up unti
Read more