Skip to main content

Working With FCK editors

I had troubles working with FCK editors using QTP.
As these editors are recorded as “WebElement” it is not possible to perform “Set” operation on them
I came across two posts which talk about dealing with this issue,
 
One is of Tarun’s where in talks about using “object” as well as “DeviceReplay” methods which could be used to simulate control on FCK editor
He suggests not using “object” for browsers other than IE as it is supported only in IE
 
 
Browser("testB").Page("testP").Frame("Frame").WebElement("WebElement").object.innerText = "Text
Browser("testB").Page("testP").Frame("Frame").WebElement("WebElement").object. innerHTML
= "<h1>Text</h1>
 
 
While other method uses object “DeviceReply” object to exercise object on which control is brought.
 
'Click on Application Object
Browser("testB").Page("testP").Frame("Frame").WebElement("WebElement").Click
 
'Create device replay object
Set oDR = CreateObject("Mercury.DeviceReplay")
 
'Send some text
oDR.SendString "Text Text"
 
'Deallocate Object
oDR = Nothing
 
There is one more portal which provides more detail information it – Advanced QTP, did not have time to go through it
 
THanks,
Tarun K
 
 

Comments

Popular posts from this blog

How to write bad UI automation code (a formal guide)

You might find umpteen resources on learning to write UI automation. But rarely you find any guide on writing bad automation code. Bad automation code is not actually "bad" especially when you consider following - Bad automation code keeps you job safe. Well who can understand the code other than you. Gives you an opportunity to ask for more raise as you are the only one who can maintain the code you write Lets you keep your head up as you the geek of your company who knows that abstruse code  Now coming to writing bad automation code, here are some silver bullets - Record and Replay is the core or writing good (read bad) automation code. It has so many advantages which just out do many others. Biggest being you don't have to write any good code (read bad), tool does it for you. The way to convince decision owners in to enlightening is to let them know that record and replay does not require any special skills. Even your HR can do this.

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can