| Cannot change textboxes with Selenium for testing purposes [message #76151] |
Fri, 29 February 2008 18:05  |
Eclipse User |
|
|
|
Originally posted by: patrick.f.machado.criticalsoftware.com
Hi all,
I've been trying (with no success) to interact with RAP textboxes with
selenium (with qooxdoo extension), for testing automation purposes.
I've read the http://wiki.eclipse.org/RapUITesting page.
In the end it mentions that selenium type command does not work with
texboxes.
However, I've been investigating a bit on my own on this subject and have
been able to write text into the textfield in two ways (using firebug).
a) Directly writing a value into the input box associated with the rap
text field (and consequently qooxdoo widget) with
document.getElementById(idOfTheInputField).value = 'some value'.
b) Using the qooxdoo accessors to change the corresponding widget
value, with
document.getElementById(idOfTheWidgetDiv).qx_Widget.setValue ('some value')
Both ways show the value changing (visually) in the field, but when some
code accesses the text field (in the RAP level), it remains unchanged.
I've tried (with selenium) to replicate every event in the input field,
but with no success (again the value changes in the input field, but the
upper-level widget at RAP level remains unchanged):
this.selenium.mouseOver(element);
this.selenium.mouseMove(element);
this.selenium.mouseDown(element);
this.selenium.fireEvent(element, "focus");
this.selenium.mouseUp(element);
this.selenium.click(element);
this.selenium.keyDown(element, "s");
this.selenium.keyPress(element, "s");
this.selenium.keyUp(element, "s");
this.selenium.mouseOut(element);
this.selenium.fireEvent(element, "change");
this.selenium.fireEvent(element, "blur");
Does anyone have any insight on what could be going on here?
|
|
|
| Re: Cannot change textboxes with Selenium for testing purposes [message #77089 is a reply to message #76151] |
Thu, 06 March 2008 12:50  |
 Benjamin Muskalla
Messages: 237
Registered: July 2009 |
Senior Member |
|
|
Hi patrick,
as I mentioned on the wiki page the selenium extension for selenium is
just an prototype. Since then the qooxdoo team cared about the testing
problem by organizing their own selenium extension. I think it should be
no problem to replace the one mentioned in the wiki by the one developed
by the qooxdoo team.
Take a look at http://qooxdoo.org/documentation/contrib/simulator for
more informations about testing qooxdoo applications.
Greets
Benny
Patrick Machado wrote:
> Hi all,
>
> I've been trying (with no success) to interact with RAP textboxes with
> selenium (with qooxdoo extension), for testing automation purposes.
>
> I've read the http://wiki.eclipse.org/RapUITesting page.
> In the end it mentions that selenium type command does not work with
> texboxes.
>
> However, I've been investigating a bit on my own on this subject and
> have been able to write text into the textfield in two ways (using
> firebug).
> a) Directly writing a value into the input box associated with the rap
> text field (and consequently qooxdoo widget) with
> document.getElementById(idOfTheInputField).value = 'some value'.
> b) Using the qooxdoo accessors to change the corresponding widget
> value, with
> document.getElementById(idOfTheWidgetDiv).qx_Widget.setValue ('some value')
>
> Both ways show the value changing (visually) in the field, but when some
> code accesses the text field (in the RAP level), it remains unchanged.
>
> I've tried (with selenium) to replicate every event in the input field,
> but with no success (again the value changes in the input field, but the
> upper-level widget at RAP level remains unchanged):
> this.selenium.mouseOver(element);
> this.selenium.mouseMove(element);
> this.selenium.mouseDown(element);
> this.selenium.fireEvent(element, "focus");
> this.selenium.mouseUp(element);
> this.selenium.click(element);
> this.selenium.keyDown(element, "s");
> this.selenium.keyPress(element, "s");
> this.selenium.keyUp(element, "s");
> this.selenium.mouseOut(element);
> this.selenium.fireEvent(element, "change");
> this.selenium.fireEvent(element, "blur");
>
> Does anyone have any insight on what could be going on here?
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03841 seconds
] 
Search
Help
Register
Login
Home
