Sunday, July 12, 2009

FlashSelenium java client v1.0 released

FlashSelenium java client is now compatibility with Selenium RC 1.0.

A few problems were reported for FlashSelenium when used with the newest version of Selenium RC, SRC version 1.0.

The issues were mainly related on how FlashSelenium and Selenium RC were dealing with the object id for the Flash object.

A fix has been updated for the FlashSelenium java client. The other FlashSelenium clients are being fixed shortly.

2 comments:

VIJAY said...

Hi Team,

Still I am facing an issue in accessing Flex elements using flex objects.
Following error message is show for all the operations...

https://www.blogger.com/comment.g?
blogID=6856830647321234822&postID=6699512121797663320&page=1&pli=1

The above link shows some kind of solution!!!, But I have followed the steps given
by them. It is not working as expected. It shows the same error

"com.thoughtworks.selenium.SeleniumException: ERROR: Threw an exception: Object
doesn't support this property or method
at
com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError
(HttpCommandProcessor.java:97)
at com.thoughtworks.selenium.HttpCommandProcessor.doCommand
(HttpCommandProcessor.java:91)
at com.thoughtworks.selenium.HttpCommandProcessor.getString
(HttpCommandProcessor.java:262)
at com.thoughtworks.selenium.DefaultSelenium.getEval
(DefaultSelenium.java:443)
at com.thoughtworks.selenium.FlashSelenium.call(FlashSelenium.java:57)
at com.thoughtworks.selenium.FlexUISelenium.at(FlexUISelenium.java:62)
at CalculateSumTest.sumForValidNumbers(CalculateSumTest.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall
(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run
(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively
(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate
(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate
(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate
(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild
(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild
(BlockJUnit4ClassRunner.java:44)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at org.junit.internal.runners.statements.RunBefores.evaluate
(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate
(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run
(JUnit4TestReference.java:45)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)

It blocks the basic functionality support mentioned by selenium - flex interface.
Since we wanted to test our application with selenium-flex API support, kindly
provide alternate option to resolve the above issue.

Movies Gallery 2011 said...

Such a wonderful post. Thanks for the share.
Android phone app development| Google android app development|