Skip to main content

Excel Automation and a palatable QTP Suite

 

Excel automation and VBScript can be used to create a test suite that can control the run sequence of QTP scripts and present a Summary report of the automation run cycle.

Its simple enough to double-click an icon and the VBScript program will create an excel sheet, populated with all the scripts from a Test folder. Here’s the folder structure:

image

Click here to get the files.

 

The CreateSuite.vbs program creates an excel sheet ..

image

.. and populates it with all the QTP scripts from the Tests folder (folder hierarchy within the Tests folder does not matter, a valid script folder will be fetched).

image

Here’s how the excel sheet looks after running the CreateSuite program:

image

This Test Suite has been created in the TestSuite folder, as the Suite.xls file:

image

Once the list of tests is available, one can choose to configure a subset of the listed tests to be run, like in the case below, we turn off the fourth test:

image

Now that the list of tests to be run is ready, we can double-click the SuiteRunner.vbs program to get the automation run started:

image

Some features of the Runner:

  1. The Suite Runner will read and run the scripts row-by-row.
  2. All scripts that are marked as Y in the Run ? column and that have a Not Run or a Failed result will be run.
  3. The full Suite can be iterated to run multiple times, for failed tests to get a chance to run in case some unexpected network state had prevented the earlier run. The last attempted iteration number is noted in the column Suite Cycle Itr.
  4. The Start and End times of each test are noted in the relevant columns.
  5. The Test Run Result is noted and highlighted with appropriate color in the Result column.

image

This excel sheet can now be used for further analysis of failures and reporting the same to the Stakeholders!

Comments

Popular posts from this blog

Microsoft Test Manager – FUEL for test automation

(this is a follow-up post to this one:  http://sudiptopaul.blogspot.com/2011/12/using-aspnet-page-state-and-theme-to.html ) Traditionally Test Management and Test Automation tools have been remotely related to each other. Microsoft’s Test Manager changes this - Manual Testers contribute effectively by creating action recordings for each test Common portions of test steps can now be grouped into what is called as Shared Steps – again manual tester can create independent action recordings for these Test Manager enables these action recordings to serve as active inputs to test automation – separate class is created for each test case, and a reusable function for each shared step This is very elegant as it saves the test automation engineer an amount of time required to refactor common portions of longish test path recordings The Manual Tester gets to contribute in the Keyword definition phase – an important thing to do, because they are the subject matter experts! Here’...

Hello World in iPhone

meines erstes iphone Programm - Gemacht durch Code

Using ASP.net Page state and theme to create Color effects on buttons – a Disco UI

  About the app - how the UI color effects juggle:   The non-crossing activities for a specific button – Button_Red   Click here for the “VS2010 Web Developer Express” code for reference.   After building the app, one can choose to deploy the web app to IIS rather than the default VS Development server. Deployment is only a few steps: 1) Build the release version of the app 2) Build the deployment package: A deployment package is created as a zip file: 3) Open the IIS Manager and import this app package Follow the wizard to deploy the package as a web app.   Run the app and here’s how the website looks:   This post will have a follow-up post on the Microsoft Test Manager and CUIT for a testing perspective!