Test Automation Ecstasy

In the CI (Continuous Integration) world, we would be in the position to trigger UFT/QTP scripts from outside of ALM/QC and there we may have 2 options like; 1. Running UFT tests stored in plain Windows File System folder 2. Running UFT tests stored in ALM Both these options are being utilized by lot of testers effectively and working great. Here I would like to give some light on what if we need to update results to particular test set instance in ALM while triggering tests from outside of ALM.  You should have seen the result options in the dialog which pops up when we are trying start running from UFT/QTP itself and we will select the option and hit OK to start running. Here we need to select those options from API. VBScript: Sub LaunchAndRunUFT()     Dim oUFT, appUFTResults, uftTestParamDef, uftTestParams, oFSO          'Launch UFT     Set oFSO = CreateObject("Scripting.FileSystemObject")     Set oUFT = CreateObject("QuickTest.Application")

How to generate HTML report with inbuilt screenshots? Lot of automation testers would come across this path while trying to integrate their automation solution with some test management tool or trying to send the execution report to management team. The main issue we face here is that we need to attach the screenshots also while sending or uploading into another tool. What would you think if we can convert the image into bytes and store it inside the HTML itself? Yes. You are right. We can attach the screenshots and report statements in one single html file and easily we can attach or send it to anybody. Function convertImageToBytes(strScreenshotFilePath)   Dim streamInput, bytesStream, oDOM, tmpElement      Set streamInput = CreateObject("ADODB.Stream")   Set oDOM = CreateObject("Microsoft.XMLDOM")     streamInput.Open   streamInput.Type = 1  ' adTypeBinary   streamInput.LoadFromFile strScreenshotPath   bytesStream = streamInput.Read        Set

Most of us should have heard about the term BDD - Behavious Driven Development. In this post, I would like to give some intro about familiar BDD framework called Cucumber and why we need BDD. Why BDD? Once people started moving to Test Driven Development (TDD), it helped a lot interms of reducing the bugs in development stage itself as every feature was developed by creating smaller unit tests, making it FAIL and coding the functionalities to make it PASS. But eventually, the BAs and testers are not able to follow these testing practices and thus gap in communication which lead to lot of mis-understanding the features/requirements. So, experts wanted a framework which should take inputs like normal people speaking English and should run the tests based on those requirement. Also this requirement will support as documentation of features to understand by testers/BAs/devs. Thus BDD was born. BDD keywords: Given, When, Then and And Example: Scenario: Login to Facebook  Giv

Based on the knowledge gathered from QA and DevOps experts, presenting a simple graphic which represents how actually the CONTINUOUS delivery works. Also this will help to differentiate each from other.

As current agile development process keep on expecting more testing with continuous integration stuff, I am going to give brief summary about how we can integrate the CI process with Jenkins. Pre-Requesties: 1. Your Selenium project 2. Your Selenium and TestNG lib locations 3. Jenkins installed. Ensure IIS in your machine installed and you can access Jenkins Dashboard using  http://localhost:8080/ Before creating a job under Jenkins, try to run your selenium tests from command line. Selenium - CommandLine: Let's say, you have project called SeleniumProject under C:\Eclipse folder. Assume you have all your JAR files (Selenium Jars, TestNG Jars, etc) under C:\Eclipse\JARs  folder. Now you can prepare your command. 1. Go to Project location cd "C:\Eclipse\SeleniumProject" 2. Execute your testng.xml suite by setting the requied class path. java -cp "bin;..\JARs\*" org.testng.TestNG testng.xml -cp means class path bin - bin path to look into cl

While doing automation on UI, we will face lot of scenarios like Object not identified as expected type and will scratch our head how to simulate such object set, click, etc. We have some options to simulate actions on such controls using WScript.Shell or Mercury.DeviceReplay The only thing, we need to instruct the those APIs at whichposition exactly it need to perform the actions. You can do with absolute poistion: x = yourObject . GetROProperty ( " abs_x " ) + ( yourObject . GetROProperty ( " width " ) / 2 ) y = yourObject . GetROProperty ( " abs_y " ) + ( yourObject . GetROProperty ( " height " ) / 2 ) Set MerRply = CreateObject ( " Mercury.DeviceReplay " ) MerRply . MouseClick x + 5, y, LEFT_MOUSE_BUTTON You can use relative position: x = yourObject . GetROProperty ( " width " ) / 2 y = yourObject . GetROProperty ( " height " ) / 2 yourObject . Click x, y, LEFT_MOUSE_BUTTON If