style="display: none; visibility: hidden;" are not found by xebium where as SeIDE finds them about xebium

[cwortel]

Please let us know your Firefox version, this would be helpful

[mpadma]

Hi,

I am using Firefox 4.0 version

Thanks,
Padma

On Thu, Sep 29, 2011 at 1:47 PM, Cirilo <
[email protected]>wrote:

Please let us know your Firefox version, this would be helpful

Reply to this email directly or view it on GitHub:
#20 (comment)

[cwortel]

It seems it is a timing issue, do you run your test in Selenium IDE at full speed? If not you might want to add a delay in your Xebium tests as well:

Somewhere in the beginning of your script add:
| set step delay to | 1000 |

This results in a pause of one second after each action being executed.

Or just add a single pause prior to the failing step:
| ensure | do | pause | on | 3000 |

This esults in a 3000 ms wait.

These workarounds are not the most pretty way of creating testscripts, but they might be the solution to your problem for know. Please let us know if this is any help.

[mpadma]

I tried with waitForElementPresent as I said in the first description.. but
still it didnt work..
Now I tried with ur step
| ensure | do | pause | on | 3000 |
then I still got the following error..

Performing | pause | 3000 |
15823 [Thread-1] INFO com.xebia.incubator.xebium.SeleniumDriverFixture

• Performing | clickAndWait | //div/li/ul/li[2]/a/span |
  15885 [Thread-1] ERROR
  com.xebia.incubator.xebium.SeleniumDriverFixture - Execution of
  command failed: Element is not currently visible and so may not be
  interacted with
  System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1',
  java.version: '1.6.0_25'
  Driver info: driver.version: RemoteWebDriver

I tried with
| set step delay to | 1000 |
then also got the following error

Performing | pause | 3000 |
19267 [Thread-1] INFO com.xebia.incubator.xebium.SeleniumDriverFixture

• Performing | clickAndWait | //div/li/ul/li[2]/a/span |
  19295 [Thread-1] ERROR
  com.xebia.incubator.xebium.SeleniumDriverFixture - Execution of
  command failed: Element is not currently visible and so may not be
  interacted with
  System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1',
  java.version: '1.6.0_25'
  Driver info: driver.version: RemoteWebDriver

I dont think this is about delay problem

Thanks

On Thu, Sep 29, 2011 at 7:34 PM, Cirilo <
[email protected]>wrote:

It seems it is a timing issue, do you run your test in Selenium IDE at full
speed? If not you might want to add a delay in your Xebium tests as well:

Somewhere in the beginning of your script add:
| set step delay to | 1000 |

This results in a pause of one second after each action being executed.

Or just add a single pause prior to the failing step:
| ensure | do | pause | on | 3000 |

This esults in a 3000 ms wait.

These workarounds are not the most pretty way of creating testscripts, but
they might be the solution to your problem for know. Please let us know if
this is any help.

Reply to this email directly or view it on GitHub:
#20 (comment)

[cwortel]

Thanks for trying those options out. Sorry to hear it did not solve your problem. Xebium v.0.3 comes with a fixed dependency on a now backdated webdriver/selenium2.0 version. One more thing you could try is to try is using a more recent version of Xebium, this however works best with Firefox 6.x or higher.

I've uploaded the latest version of the jar-with-dependencies v0.5-SNAPSHOT to https://github.com/xebia/Xebium/downloads

Hope to be of help

[mpadma]

Thanks for ur support n quick replies. :) I was having a trouble with SeIDE with Firefox6.. it was not starting at all. So thats why I am using this version of Firefox.

[cwortel]

This issue was unintentionally closed, reopened it.

[eskape]

Hi Padma.

Seems that you are clicking on an element that is not visible. See the following message in your output:

"Element is not currently visible and so may not be interacted with"

Please add some time out before clicking on the element to see whether your element is visible at that moment.

[eskape]

We solved this issue with Padma

[mpadma]

we solved it together.
Basically the problem was due to the use of " css=span:contains('someTextOnUrPage') " which didnt work with the version of xebium I had
There is a possibility that xpath can be ambiguous in our page.. Not sure whether there is another element with same xpath I am finding for.

solved by updating xebium to the xebium-0.5-0 and also the dependecy jar to the xebium-0.5-SNAPSHOT-jar-with-dependencies
Thanks for that.