This repository was archived by the owner on Jun 27, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 27, 2019. It is now read-only.
Fitnesse Tests Failing #134
Description
Hi,
I have selenium tests for our app (made from ExtJs 5). I then formatted them through Xebium and i'm testing them out in Fitnesse. However, the tests are failing and it seems the app and its components are not loading. I've tried start browser=firefox and phantomjs but both have time out exceptions while looking up elements. Any ideas why it's not working? Is it ExtJs related? The tests are working fine in Selenium IDE. Thanks!
Activity
vin31 commentedon Jul 21, 2014
I think it's either the app didn't load at all or there's something wrong with the way I locate the elements using xpath. Additional information from my logs:
INFO com.xebia.incubator.xebium.SeleniumDriverFixture - Performing | waitForElementPresent | xpath=//div[contains(Ivan Dyachkov (@id), 'action-type-radiogroup')] | 5000 |
[ERROR - 2014-07-21T09:10:09.808Z] WebElementLocator - _handleLocateCommand - Element(s) NOT Found: GAVE UP. Search Stop Time: 1405933809745
13327 [main] INFO com.xebia.incubator.xebium.SeleniumDriverFixture - Command 'isElementPresent' returned 'false' => not ok, expected '5000'
gerbrand commentedon Aug 27, 2014
I think I have similar or the same problem. The problem occurs when:
Here's a stacktrace:
Command duration or timeout: 392 milliseconds
Build info: version: '2.42.2', revision: '6a6995d31c7c56c340d6f45a76976d43506cd6cc', time: '2014-06-03 10:52:47'
System info: host: 'gerbrand-Lenovo-G500', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-32-generic', java.version: '1.7.0_60'
Session ID: 64ad5020-2e87-11e4-8105-33158dad5fae
Driver info: com.xebia.incubator.xebium.fastphantomjsdriver.FastPhantomJSDriver
Capabilities [{platform=LINUX, acceptSslCerts=false, javascriptEnabled=true, browserName=phantomjs, rotatable=false, driverVersion=1.0.3, locationContextEnabled=false, version=1.9.0, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=false, browserConnectionEnabled=false, webStorageEnabled=false, nativeEvents=true, proxy={proxyType=direct}, applicationCacheEnabled=false, driverName=ghostdriver, takesScreenshot=true}]
at com.thoughtworks.selenium.webdriven.SeleneseCommand.apply(SeleneseCommand.java:44) [selenium-java-2.42.2.jar]
at com.thoughtworks.selenium.webdriven.Timer.run(Timer.java:40) [selenium-java-2.42.2.jar]
at com.thoughtworks.selenium.webdriven.WebDriverCommandProcessor.execute(WebDriverCommandProcessor.java:143) [selenium-java-2.42.2.jar]
at com.thoughtworks.selenium.webdriven.WebDriverCommandProcessor.doCommand(WebDriverCommandProcessor.java:73) [selenium-java-2.42.2.jar]
at com.xebia.incubator.xebium.SeleniumDriverFixture.executeCommand(SeleniumDriverFixture.java:583) [file:/home/gerbrand/workspace/Fundeon/Xebium/target/classes/]
at com.xebia.incubator.xebium.SeleniumDriverFixture.getCommandOutput(SeleniumDriverFixture.java:550) [file:/home/gerbrand/workspace/Fundeon/Xebium/target/classes/]
at com.xebia.incubator.xebium.SeleniumDriverFixture.executeCommand(SeleniumDriverFixture.java:531) [file:/home/gerbrand/workspace/Fundeon/Xebium/target/classes/]
at com.xebia.incubator.xebium.SeleniumDriverFixture.executeAndCheckResult(SeleniumDriverFixture.java:499) [file:/home/gerbrand/workspace/Fundeon/Xebium/target/classes/]
at com.xebia.incubator.xebium.SeleniumDriverFixture.executeDoCommand(SeleniumDriverFixture.java:457) [file:/home/gerbrand/workspace/Fundeon/Xebium/target/classes/]
raboof commentedon Jun 29, 2015
Does setting the 'useFastSeleniumEmulation' option help?
raboof commentedon Feb 15, 2016
Loyvin Ramirez (@vin31) I'm afraid this is a bug in the Selenium IDE to Xebium exporter.
Your command is:
| check | is | waitForElementPresent | xpath=//div[contains(@id, 'action-type-radiogroup')] | 5000 |. This does not make sense:waitForElementPresentwill doisElementPresentuntil that succeeds - i.e., returnstrue.Then you're comparing the output to
5000- which does not make sense, as this is a command that returns a boolean. This is reflected in the error message:Command 'isElementPresent' returned 'false' => not ok, expected '5000'I'm marking this as a bug in the Selenium IDE exporter. Note that use of the Selenium IDE for exporting tests is discouraged, and we're not actively fixing bugs there, though we will review pull requests in that area.