Although unrelated to "this" blog in particular, we now have the RC client(s) to test Silverlight applications using Selenium RC. The project is hosted here and currently has the Java and .NET clients in the "Downloads" section.
Kudos to Sai and Geetan who helped us in understanding Silverlight internals and verifying the client(s) against their prototype. Great job guys!
Subscribe to:
Post Comments (Atom)
1 comment:
Still, IE 7, FF 3.0 issues were not fixed it seems....
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.
Post a Comment