Relevant Codes

A Test Development Resource for HP QuickTest Professional.

QTP Siebel Error: Test Execution halts when a SiebButton is clicked

by Anshoo Arora on October 15, 2009

We had an issue with one of the SiebButton objects’ in our environment. When we executed a statement to click on this particular SiebButton, the next statement would not execute. What happens is, as we click this particular SiebButton, a Dialog box pops up immediately. For some reason that we have not been able to figure out, the execution marker from the SiebButton(“”).Click statement will not move to the next line. Instead, it just got stuck there, and stood there, forever.

We suspected that it may be because of a Modal Dialog that appears in the application preventing QTP from accessing the button. Another reason could be the poor performance of QTP & Siebel working together.

Below, you will see a rough demonstration of what happens:

'Click Sieb Button
SiebApplication("myApp").SiebScreen("myScreen").SiebView("myView")_
    .SiebApplet("myApplet").SiebButton("myButton").Click  'Dialog Opens and test halts here

'Execution marker never proceeds to the next statement:
Dialog("micclass:=Dialog").WinButton("text:=OK").Click

We were not able to figure out why the execution marker would not move on to the next line. We still haven’t figured it out. However, we found a workaround!

Instead of using one of the Siebel methods/descriptions to click the SiebButton, we used the Web framework (UI) event to click the SiebButton instead, which is viewed as a WebElement with just the Web-Addin loaded:

Browser("title:=Siebel.*").WebElement("text:=myButton", "index:=0").Click

This made the execution marker jump to the next execution line immediately, solved the issue that we were having and our script has been working brilliantly so far! If you have encountered an issue like this, please try this solution and even though I cannot guarantee that it will work, but chances are excellent that it might. :)

Credits go to Todd Mescher for working together with me to come to this fantastic resolution for an issue as strange as this. Thank you, Todd.

{ 5 comments… read them below or add one }

1 justnotkidding October 27, 2009 at 5:34 am

hi,
I want to know if we have to start automating Siebel web client, how do we proceed
We have the demo version of Siebel Client (for call centre Module)installed from Oracle, where we are able to see the functionalities(like account, opportunities, Service Request, Activities etc)

We have a licensed version of QTP 9 and also Siebel add in installed.

Please guide me in this.

Reply

2 Anshoo Arora October 27, 2009 at 8:35 am

Hello,

This article gives a brief introduction to Siebel and describes a few settings that should be set in order to successfully start testing Siebel. You will find concepts of different types of Siebel Objects here.

Even though Siebel is quite interesting to automate, and generally quite straight-forward, it would really help you if you scan over the methods of Siebel objects because it works quite differently from any other application, mainly because it has its own methods that are not found in any other application environment.

If you have any questions after reading the articles, please post here and I will try my best to help you.

Reply

3 Tarun Lalwani November 18, 2009 at 2:44 am

The article below also shows few more methods to workaround a Modal dialog issue in QTP

http://knowledgeinbox.com/articles/qtp/how-to/how-to-work-with-modal-dialogs-in-qtp/

Reply

4 Anshoo Arora November 18, 2009 at 2:00 pm

Thanks for sharing the article, Tarun :)

Reply

5 QTP_Errors July 30, 2010 at 3:22 am

I had similar kind of problem and was struggling for past 3 Days and after trying as per above solution..It worked for me..Thank You so much for providing such a great solution and it really worked for me..

Thank You

Reply

Leave a Comment

Previous post:

Next post: