Closing Multiple Browsers at a time

The following script will close multiple browsers that are currently open:

Method 1:

Set BrowserObject=Description.Create()

BrowserObject("micclass").value="Browser"

Set BrowserChildObjects=Desktop.ChildObjects(BrowserObject)

For i=0 to BrowserChildObjects.count-1

BrowserChildObjects(i).close

Next

Method 2: By closing the running process

SystemUtil.CloseProcessByName "iexplore.exe"

Method 3: If we want to exclude a particular browser, we have to make modification to the 1st script

Set BrowserObject=Description.Create()
BrowserObject("micclass").value="Browser"

Set PageObject=Description.Create()
PageObject("micclass").value="Page"

Set BrowserChildObjects=Desktop.ChildObjects(BrowserObject)
For i=0 to BrowserChildObjects.count-1

    Set PageChildObjects=BrowserChildObjects(i).ChildObjects(PageObject)(0)
    If Instr(PageChildObjects.GetROProperty("title"),"")=0 Then 'Provide the appropriate title of the page within the double quotes

        BrowserChildObjects(i).close

    End If

Next

HP Quick Test Professional

By far one of the best commercial tool available in the market for Software Test Automation.

It goes beyond GUI (Graphical User Interface) Level Testing and caters not only to web applications but also    to Web services, Database Testing, Extensible Markup Language (XML's) , Windows Applications., etc....

In this section we will delve deep into the features of QTP as a tool and how to maximize its advantages.

Keep checking out this space for more.... :)

Why Automation???

"30k test cases and the time limit to test is just in an excess of a week's time"
Is it possible???
May be or may not..... no word to the client... a tentative "Yes"... we will try to do it.... but...
Ifs and buts galore... and rightly so... effort is huge and resources at disposal the least.... and we end up loosing Client's confidence....

Well its just one of the simple example to depict "Test Automation" is here to stay... it is now a very integral part of our Software Testing Life Cycle and its a parallel Software Development Effort in the hugely process driven Software Testing Life Cycle.

Reasons galore and I think I need not explain much to my readers as to why we go back again to some kind of development process while Testing a Developed Software/Application.

So lets get started with the process of Test Automation by digging in deep into the tools that we have at our disposal or let's do a research on the development acumen we have within ourselves to automate a manual process.

Having said that, I would like to stress on the fact that "Software Testing" can never be all Automation dependent... Automation is an extension to Software Testing process in a Technical way... It can never replace a human effort in this stream.... So I welcome anyone who is interested to improve the process to my postings...which may help you in many ways.