UnsupportedOperationException since latest changes about xebium

[amolenaar]

Hi,

That should not happen (our own tests seem to be fine). Can you attach a
sample of a failing test? I'll check it out
Op 25 nov. 2012 16:23 schreef "Christian Kreutzer" [email protected]
het volgende:

Hi there,

since the latest updates (the moving of webdriver instance creation to
seperate class) i get only UnsupportedOperationException when trying to run
some tests:

EXCEPTION:java.lang.UnsupportedOperationException: setTimeout
at
org.openqa.selenium.WebDriverCommandProcessor.execute(WebDriverCommandProcessor.java:141)
at
org.openqa.selenium.WebDriverCommandProcessor.doCommand(WebDriverCommandProcessor.java:74)
at
com.xebia.incubator.xebium.SeleniumDriverFixture.executeCommand(SeleniumDriverFixture.java:466)
at
com.xebia.incubator.xebium.SeleniumDriverFixture.setTimeoutOnSelenium(SeleniumDriverFixture.java:193)
at
com.xebia.incubator.xebium.SeleniumDriverFixture.startBrowserOnUrl(SeleniumDriverFixture.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at fitnesse.slim.MethodExecutor.callMethod(MethodExecutor.java:43)
at fitnesse.slim.MethodExecutor.invokeMethod(MethodExecutor.java:30)
at fitnesse.slim.MethodExecutor.findAndInvoke(MethodExecutor.java:53)
at
fitnesse.slim.FixtureMethodExecutor.execute(FixtureMethodExecutor.java:18)
at
fitnesse.slim.StatementExecutor.getMethodExecutionResult(StatementExecutor.java:189)
at fitnesse.slim.StatementExecutor.call(StatementExecutor.java:179)
at fitnesse.slim.Statement.callMethodAtIndex(Statement.java:104)
at fitnesse.slim.Statement.call(Statement.java:97)
at fitnesse.slim.Statement.execute(Statement.java:77)
at fitnesse.slim.ListExecutor.execute(ListExecutor.java:36)
at fitnesse.slim.SlimServer.executeInstructions(SlimServer.java:81)
at fitnesse.slim.SlimServer.processTheInstructions(SlimServer.java:73)
at fitnesse.slim.SlimServer.processOneSetOfInstructions(SlimServer.java:57)
at fitnesse.slim.SlimServer.tryProcessInstructions(SlimServer.java:43)
at fitnesse.slim.SlimServer.serve(SlimServer.java:30)
at
fitnesse.socketservice.SocketService$ServerRunner.run(SocketService.java:95)
at java.lang.Thread.run(Thread.java:722)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/54.

[ckreutzer]

Hi Arjan,

i can reproduce this behaviour with the xebium example test cases. i used a fresh git clone of the repo and did a completly fresh build after removing all jars from ~/.m2 and ~/.ivy2 --> result stays the same :-/

cheers,
Chris

[amolenaar]

I pushed my most recent changes. They should fix this (note to self: push commits iff everything works)

[ckreutzer]

now i get an compilation error. Seems like dependancy on org.apache.commons.lang is missing in the pom file (?)

[raboof]

I can reproduce the compilation error with a fresh clone and 'mvn package'.

Added a dependency to commons-lang 2.6 (not the newer 3.1 - should be no problem as they can peacefully co-exist).

'mvn package' now succeeds for me. ('mvn -Pfitnesse test' hangs, but that's another issue and possibly local to my machine).

Should we set up a CI environment to catch issues like this?

[hierynomus]

You could use the cloudbees buildhive (https://buildhive.cloudbees.com/) platform to setup a CI environment.

[ckreutzer]

@raboof: thanx for the fix. will try it later.
Setting up an CI env sounds like a good plan to me

[raboof]

(made a seperate issue for a CI server, #55)

[amolenaar]

Thanks.

I forgot to push my last change.

[ckreutzer]

works now for me. i think we can cose this issue