TestAutomation

The testing hosts is the kind of functionality which HP ALM provides, so that you don't need to engage your machine for any automation scripts execution. You can define any local machines or servers as testing hosts. It will help you to have the scripts and results in HP ALM itself and also don't need to look for any spare machine or wait till you leave office to start the execution. Most of the big organizations provides the testing hosts to there projects teams so that these hosts can be shared across projects. So in these cases, you just need to contact the centralized team in your organization to add those testing hosts in your project. But if the organization doesn't have a centralized pool of testing hosts then you can define your own testing hosts and use it for any automation test execution. 1. Go to Testing hosts in under Lab Resources in HP ALM. 2.  Click on new testing hosts button and fill in the details as shown in below screenshot: 3. After a...

1. You should have PC Tester profile in ALM to create new Build verification suite. 2. The functional test sets should be created in ALM Test Lab. The functional test sets are the test set in Test Lab with Type as "Functional". 3. The Is Valid flag for the functiona test set should be Y, so that it will be available for build verification suite. 4. You can add any number of functional Test sets in the build verification suite. 5. After creating build verification suite, you need to add testing hosts in the your ALM project for build verification suite. 6. The testing hosts need to be added in the Testing hosts tab under Lab Resources in ALM 11.5. I will add more on adding testing hosts in my next post.

Uploading the document to ALM from local machine                 strFileName =LocalmachinePath & strFileName                 FileDescription = "Test"                                                 Set TDConnection = QCUtil.TDConnection                 Set treeManager = TDConnection.TreeManager                 Set node = treeManager.nodebypath(ALMFolderpath)               ...

This function connects to QC test plan and gets the node of the folder you want the attachement from. Public Function GetAttachmentFromFolder(FolderName, FileName, OutPath)                 Set TDConnection = QCUtil.TDConnection                 Set treeManager =  TDConnection.TreeManager                 Set node = treeManager.nodebypath(FolderName)                                      GetAttachmentFromFolder = GetAttachmentFromTestObject(node, FileName, OutPath) End Function This function gets the attachment from the testobject which is extracted from the node which is...

Below are the prep-requisites which are very much required before executing your automation scripts created in UFT from ALM: Connection of UFT with ALM for loading automation scripts You should have admin rights on the machine to make first connection of UFT with ALM. After first connection, the admin rights are not required. Sometimes instead of having admin rights the connection, UFT is not able to make connection with ALM. In those scenario's the UFT setup needs to be done through the setup file on your machine instead of some shared library or drive. Click on ALM -> ALM Connnection and Enter username and password. Click on connect button. Select the Domain and project then click on login button.      2.  All resources in you automation scripts should be uploaded in ALM The shared object repository getting used in automation script should be saved in ALM Test Resources tab. And this should be referenced in your automation scripts under test se...