Sometimes we use by pass logic or work around to make a testcase pass. This can give a false positive result. Actual bug can be hidden behind this. So make sure you workarounds are limited and well tested.Discussing about the automation scripts ,scenarios and what automation is actually doing may give automation team a better idea and understanding.This is also reduce the pressure on automation team. It will clear the road blocks.So communication also plays a vital role. So don’t be afraid of asking or questioning the area which you don’t know.
A significant benefit of hybrid framework is the ability to support multiple browsers,platforms and technology stacks. So take proper advantages of capabilities,object clesses and business classes.
To get success via hybrid framework, management support is not only necessary but also critical.but the expectation from automation should be realistic.Even though we are using a hybrid framework, the main objective should be to pick up a small testcases and automate.The small step forward will give automation and the underlying concept a huge boost.
In the hybrid framework, automation team can be divided into developers, executors(including report generators and analysis), functionality Automator, gatekeeper, reviewer etc.when the responsibilities are given as per knowledge level, the chance to excel with automation will go high.
We generally carried by the buzz words in the name of the framework. So migrating to a good framework may not be necessary for your organization if the current one is doing just great. So better not to reinvent the wheel or don’t change it until it is broken.
|The architecture of B.P.T framework|
BPT stands for Business Process Testing.It is a component driven framework where each business flow or sub section of a flow is represented as a component.BPT allows non technical persons,subject matter experts to quickly create test scripts and execute them.
Linking the components are inbuilt,getting dataset is also inbuilt,hence it is very easy to configure. BPT can only be used if we have Quality Center(HP test planner).We need to purchase BPT license apart from UFT and Quality Center(HP Test planner).
The “BPT” is the first web-based test design software. Mercury (nowadays HP)’s the best approach towards test automation project is to keep SME’s busy by designing automated script while the test automation engineers are busy with the coverage.
Business Process Testing is a summation of flows. And flows are divided into components.
in our traditional BPT framework automation is divided into two halves.
- one is to design the component(might be reusable or business based)
- to use them in a drag and drop manner and execute them
BTP are scenarios consists of several components. They are intended to design and verify a scenario. It is the big step forward towards shift left approach where business analysts get involved in the testing process very early of the test life cycle.
In BPT, we create business components and add/stitch them into a business process test. One business component is to test a single business action that performs a specific task in the business process.
The basic block of BPT:
- Business Process Test
- Business Specific flows
- Application Area
Business Process Test:
This section is the main flow decider. It may consist of several flows inside.
The second level of BPT framework. We are going towards definite flows from BPT’s abstraction. Flows are an aggregation of components.
To enable a flow we need to define the Application area. It is the storage or place holder of underlying components.So application area acts as a container.Object Repository, Excel, test data, recovery scenarios, and lib, etc will be placed here in order to work with Components with respect to the flow.
Most Components are written in Vbscript, majorly reusable components. They are the lowest level of concrete things that interact with UAT. Components take data and other supporting files from the Application area in order to work under a flow.
A component is the smallest set of code which does a specific task. You can say a unique functional element which cannot be subdivided. We try to maximize the usability of the component so that it can be reused at a different level. Test Process is the collection of such components.
A component is a summation of some reusable code or in advanced BPT these are the only human readable keyword. It can be functions or actions or code.
|Design of BPT|
On top of this, there are libraries available, Such as
- Project Specific lib–Flows that are common only for a specific project
- Navigation lib—A small set of functions that reads from the data table and handles navigation related queries
- Environment lib–Details of the environment are passed from here
- Common lib—Set of functions common across Projects.
Say–Do_login it is a small unique functionality of any application. It can not be further divided into pieces.
So it is an example of Components. Now, what is inside of components–some set of codes or a keyword structure that performs User Interface related activities. There it might call the Navigation lib to perform Navigation to a certain portal.
Example of Keyword-
Example of full component Do_login
for this login components, we need to initialize first then load the component
this URL will come from the navigation library
Again the launch_Browser is a common function will come from the common library.
After login, there might occur two scenarios.
- Successful login
- Failure login
There must a checkpoint to check the login operation
So the algorithm for component development is…
- Call launch_Browser(URL)
- textfield–id–set text-“abc”
- textfiled–password–set text–“XXX”
- Validation of login code
- Unload Component
Role of SME in BPT:
- Define the Business process
- Define the flow
- Ask for components
- Once the components and Application area available stitch the components to create a flow.
- Execute the test cases
Role of Automation Engineers in BPT:
- Look for flows
- Define and design application areas
- Define OR files and Library files
- Support on demand the SMEs to validate the flow.
The architecture of BPT:
So it can be told that BPT framework is a three-tier architecture. where the first tire is for higher management who look after the requirements vs testing. Management can report and assign a test,
The second tire is for automation test engineers who design the components. The major advantage of this framework that the automation test engineers do not need to know the functional flow. So they can create a component, create function library and create the Object Repository.
|The architecture of B.P.T framework|
and the last tire is for SMEs who design the test. They can select components by drag and drop. They can configure the input as many possible combinations as possible. The can debug the test plan. They can add/delete the test plan. Most importantly they can execute.
Example of BPT Design:
The first part(the light blue part of the picture) is done by the Automation engineers. in this part automation engineers design functional library, create necessary object repository files and finally create components.
Say I need to automate
- login to the portal
- create customer
So automation engineers create a component called Login. This login will use two common functions…
- editing a text filed for id
- editing a text filed for password
- click on a submit button.
Again for the second component, they create Create_customer
- editing a text filed with the name
- edit a text filed with address
- also editing a text filed with ph no
- click on a submit button.
These functions will come from function libraries. Function library might be divided into two halves–
- Pure business library
- Pure common function library
They will upload these components in Quality center.
Now the SME’s will create a test(light red part of the picture). Take these components in drag and drop manner and design the same. They will configure the input and output file as a set of data. Then they will run this test from QC. After the successful test run, they will go to the output file and will validate the result.
- Very easy for SMEs to create and test flows using the power of Automation.
- Shift left approach- hence test can be written very early in the cycle.
- Very good engagement tool that gives birth to Agile concept.
- Easy component link, flow stitching, and test data providing interface provides great speed for testing
- It is not free. It needs a license from HP. Hence it is costly.
6 latest frameworks:
Many gurus believe that manual screening is the ideal way to check out the merchandise and detect all glitches. Nonetheless, these days this strategy is not plenty of, because of the quick-modifying IT alternatives and new, much more advanced units.