1. Thanks so much! This is exactly what I needed!

    Mark Geiger

  2. No problem, do come back for more! 😉

    Rogier van het Schip

  3. Hi Rogier.

    I’ve been running a test case in both Selenium IDE and have now exported it to Xebium. I get a timeout Error in xebium but not Selenium IDE.

    What’s the reason?

    Assertions: 25 right, 1 wrong, 0 ignored, 1 exceptions (27.912 seconds)

    __EXCEPTION__:com.thoughtworks.selenium.SeleniumException: null (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 79 milliseconds
    Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
    System info: os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘2.6.32-38-generic’, java.version: ‘1.6.0_20’
    Driver info: driver.version: RemoteWebDriver


    • Hi Aditya,

      Sorry, I can’t tell from just the information you’ve sent me, there is no extra information attached to the exception and I don’t know what the test does. A way to approach this problem is to create an empty test without the timeout error and gradually copy the faulty test into the new test, line by line, running the new test after each line, until you can isolate the line that’s causing the timeout.

      Also, one question: What do you mean by ‘running a test case in BOTH Selenium IDE’?

      – Rogier

      Rogier van het Schip

      • Sorry added BOTH by mistake.

        My first error occurs on two javascript store Element and StoreEval Expressions. Does Xebium throw an error on javascript ?

        Here it is :

        | $Present= | is | storeElementPresent | on | id=id_0-Extension |
        | $choose= | is | storeEval | on | storedVars[‘Present’]==true?”id_0-Extension”:”class=addfield” |
        | ensure | do | click | on | $choose |


        • I would say this is a Selenium error, given that you receive a SeleniumException, but I’m not sure what Xebium sends to Selenium about your javascript. I can understand what you’re trying to do from the code, though. What does your output log say about these lines? Did this code work in Selenium?

          One other thought: Shouldn’t the second line be | $choose= | is | storeEval | on | storedVars['Present']==true?”id=id_0-Extension”:”class=addfield” |

          What you could also do is take this to the Xebium developers, at their Google Group.

          Interesting to know, by the way, is why FitNesse never included if, for or while constructs: Acceptance tests (FitNesse’s target) describe the behaviour of the system in a certain case, there shouldn’t be multiple paths in this behaviour. If there are, you could say they’re multiple tests. Or, as Gojko puts it: “Acceptance tests (in this case FitNesse pages) should describe the specification of what the software should do (or does in regression test), not how it the test is performed.

          Rogier van het Schip

Comments are closed.