Exception 硒异常

如何解决此异常

根元素配置

5 Jan, 2011 4:21:59 PM com.ensarm.niidle.util.logger.NiidleLogger log
SEVERE: ERROR Server Exception: sessionId should not be null; has this session been started yet?
com.thoughtworks.selenium.SeleniumException: ERROR Server Exception: sessionId should not be null; has this session been started yet?
    at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
    at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)
    at com.thoughtworks.selenium.DefaultSelenium.open(DefaultSelenium.java:335)
    at com.ensarm.niidle.web.proxy.navigators.BasicProxyNavigator.openProxy(BasicProxyNavigator.java:131)
    at com.ensarm.niidle.web.proxy.navigators.AnonymitaComProxyNavigator.initialize(AnonymitaComProxyNavigator.java:25)
    at com.ensarm.niidle.web.proxy.navigators.AnonymitaComProxyNavigatorTest.testInitialize(AnonymitaComProxyNavigatorTest.java:67)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    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:73)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
    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:46)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

---

您正在运行Selenium IDE还是RC

如果是Selenium RC，那么我注意到当实例创建不正确时会出现这种异常，例如，您需要：

selenium = new DefaultSelenium ( ... )
selenium.start ();
selenium.open ( ... )

---

您正在运行Selenium IDE还是RC

如果是Selenium RC，那么我注意到当实例创建不正确时会出现这种异常，例如，您需要：

selenium = new DefaultSelenium ( ... )
selenium.start ();
selenium.open ( ... )

---

我注意到，当selenium客户端试图对浏览器已关闭的selenium RC执行操作时，会引发此异常

Selenium RC为每个客户端分配一个会话ID，正如您在这篇精彩文章中看到的：

---

干杯，Daniel

我注意到，当selenium客户端试图对浏览器已关闭的selenium RC执行操作时，会引发此异常

Selenium RC为每个客户端分配一个会话ID，正如您在这篇精彩文章中看到的：

干杯，丹尼尔

在浏览器中运行此脚本 实际上，selenium RC将端口4444作为默认端口。有时程序在执行卸载或关闭端口之前会被中断。

在浏览器中运行此脚本

---

实际上，selenium RC将端口4444作为默认端口。有时程序在执行卸载或关闭端口之前会被中断。

如果selenium服务器未启动，则会出现错误。您必须启动服务器

---

然后执行语句selenium.start

如果selenium服务器未启动，则会出现错误。您必须启动服务器

然后执行语句selenium.start