error communicating with the remote browser. it may have died.
2016-03-10 16:05
453 查看
This usually happens when you are trying to close the same webdriver instance multiple times. Do you know what happens in
You can put that
if(driver != null) {
driver.close();
driver.quit();
}
super.teardown()? When I checked the selenium4j source, it extends junit Testcase. Your
super.tearDownwill be calling jUnitTeardown and would be killing the browser instance before
closeSeleniumSession()is called.
You can put that
closeSeleniumSession()before
super.tearDown().
if(driver != null) {
driver.close();
driver.quit();
}
相关文章推荐
- HibernateException: identifier of an instance of pojo.Order was altered from 23
- jawr使用
- ElasticSearch的ik分词插件开发
- Spark Shell由于Scala编译器原因不能正常启动
- 解析elasticsearch的config下的配置文件
- 15:39:52.027 [ActiveMQ InactivityMonitor WriteCheckTimer] DEBUG o.a.a.t.Abstract
- 互联网产品经理常用工具有哪些
- mysql中间件研究(Atlas,cobar,TDDL,Mycat)
- elasticsearch 1.1.0 mmseg 英文数字分词
- Aho-Corasick算法学习
- Java NIO 系列教程
- 优化ActiveMQ性能(zhuan)
- mysql Communications link failure Last packet sent to the server was X ms ago
- Java操作Excel完美解决方案
- 安全相关思维导图
- 关注与取消
- Java异常
- sbt为什么总抛出“java.lang.OutOfMemoryError: PermGen space”?
- JAVA 垃圾收集器与内存分配策略
- Apache Kafka:下一代分布式消息系统