TestAutomation

As we tend to run the actions in UFT/QTP by our driver script based on the flag set in the excel sheet or any input file, we don't want the flow in the solution to interrupt the execution. As the new concept of solution comes in the UFT, whenever you add any new action it gets added in the flow of the solution sequentially. For e.g. you have an existing action "Action1" and then you create a new Action with name "Action2". So in the flow the Action2 will be added after Action1 and as soon as the execution of Action1 completes Action2 will get executed. But we want the execution of actions should be derived from the driver script, So we need to remove the Action2 from the solution flow. If you try to do it directly from the solution then there is only one option "Delete Action". The workaround to remove this call is, you have to first call the Action2 from some other Action also and then delete the actions call from the solution flow as sh...

Continuing from my last post on Business Process Testing in HP ALM. In this post i will share the artifacts which will be created in UFT and getting used in creation of test cases in BPT framework. One thing always should be considered while creating these artifacts for BPT is that the UFT should be conected to ALM which has BPT license, else you will not be able to create them. The first artifact which is required is Application Area. In application area we attach all the resources like functional libraries, vbs files, object repository etc and it will be saved in ALM to the domain and project you have logged into. It will be saved in the resources tab in ALM. This application area can be used by any business component which will help us to manage the resources for different components. After creating the Application Area, the second artifact will be the business component which will have all the test steps you want to perform on the application. But as per my last f...

Continuing from where i left on Business Process Testing in my last post. I have given a brief introduction to BPT on HP ALM in my last post.  In this post, We will look into some benefits of BPT and how does BPT works. The images in the post are the courtesy of the document provided by HP when they have introduced. I found this image as the self explanatory instead of creating anything new to confuse the users.       The operations performed by any particular keyword tended to be very fine-grained or atomic. Designing a test for an entire business process required the use of hundreds of individual keywords — a time-consuming process.       Since test framework solutions consist of files with keywords and their associated data elements, subject matter experts found that they were still creating scripts, despite promises by some vendors of “script less” test design.       Traditional test framework...

HP has introduced the business process testing framework in the ALM around 2006. This framework has been introduced by keeping business analysts in mind, so that they can create the scenario as per the logical flow of the application by themselves and instead of dependent on any automation tester to create a full test case for them and then they verify the whole test script functionality. In this framework the automation testers create the business components with the logical business names. Then business analyst or functional testers can create the test cases by arranging the business components in the sequence they want. This helps the business analysts to create the different scenario's on the go instead of raising the request and waiting for the automation tester to completed the coding for this test script. Here user can give different parameters for the same component in different test cases which was not possible when users use same test cases in different scenario...

It happens many times that we want to refer to the previous run results of the test in a test set but we don't know how to go to those results. The only thing you need to do is click on the name of the test in the test set in test lab and it will open a new window called as Test instance details. This window has all the details of the test such as planned execution date, status etc. This window has different tabs one of them is Runs. The runs tab shows all the previous run details such as status, exec date, time etc. You can open the result report of any execution by just clicking that row in the table and click on the Launch Report button. You can also drill down the details of each run by clicking the run id of the run which will open a new window called as Run Details. Below are the screenshots of both the detail windows.

As we start our work to start the execution of UFT/QTP scripts through ALM, we change our scripts related to all aspects of repository linkage to script, functional libraries, input excels, uploading results files created after execution. But still when we try to start the execution from ALM the UFT/QTP is not able to open on the host and the execution is not able to take place. The basic setting which needs to be completed on the UFT/QTP for the hosts where you need to run the scripts. The user needs to open the UFT/QTP on the machine and need to go to Tools > Options and check whether the checkbox "Allow other HP products to run tests and components is checked or not. Nowadays, HP has provided this as one of the errors when you try to execute the script from ALM and if this setting is not done on the host. Its a very small step but takes alot of time to debug if you don't know the description of this option.

                              Type of Test sets in HP ALM I haven't explained the type of test sets while i have written the blog on adding testing hosts in HP ALM. And this has created a little confusion for one of the viewer. So i thought let me clarify the type of test sets here which will help you on type of testing hosts for those test sets. In HP ALM, it gives you 3 options whenever you go for creation of test sets i.e. Functional, default and Performance. As name suggests performance test automation scripts gets added to the performance test sets. And UFT/QTP scripts gets added to functional and default test sets. Below are the only differences between functional and default test sets: 1. Only functional test sets can be added to the build verification suite which users are nowadays use for continuous delivery. 2. The testing hosts used in the functional test sets are to be used from the h...