Selenium 中的自定义 Firefox 配置文件导致插件不兼容
现在这很棘手。我正在尝试使用 Firefox 和 Selenium 进行 WAP 测试。为此,我创建了一个自定义配置文件并安装了一个名为“修改标头”的插件。当我手动启动配置文件时,该插件工作正常。但是,当我将它与 Selenium RC 一起使用时,Firefox 禁用了该插件,并表示它与 Firefox 3.6.6 不兼容。这太荒谬了。如果我手动打开相同的 Firefox 配置文件,该插件可以正常工作。另外,当我更新插件(在 ff 启动的配置文件中)时,我安装了兼容性补丁,并且在重新启动 FF 后工作正常。但是,当我关闭 Firefox 并从 selenium 启动相同的配置文件时,它再次出现同样的问题。请帮忙,我的很多测试用例都是基于WAP的。您还可以建议此插件的替代品。
感谢和问候
瓦米普
Now this is tricky. I am trying to do WAP testing using firefox and selenium. For that I've created a custom profile and installed a plugin called modify headers. When I launch the profile manually, the addon works fine. But, when I use it with Selenium RC, then, Firefox disables the plugin, saying that it is incompatible with Firefox 3.6.6. This is ridiculous.If I open the same firefox profile manually, the plugin works fine. Also, when I update plugin (in the profile launched by ff),I installs a compatibility patch and works fine after restarting FF. But, when I close firefox and launch the same profile from selenium, it again gives the same problem. Please help, a lot of my test cases are based on WAP. You can also suggest alternatives to this plugin.
Thanks and Regards
Vamyip
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
您可以尝试在 Firefox 中禁用扩展兼容性检查(使用您的 Selenium 配置文件):
http://kb.mozillazine.org /Extensions.checkCompatibility
You can try disabling extension compatibility checking in Firefox (using your Selenium profile):
http://kb.mozillazine.org/Extensions.checkCompatibility
我曾经遇到过一些情况,我以为我正在加载 FireFox 3.6.x,但实际上它打开的是计算机上安装的较新版本的 Firefox (v16)。由于配置文件存储在不同的位置,因此它实际上并没有打开我认为的配置文件。
我想我应该提到它,以防它为遇到同样问题的其他人解释 varmyip 的问题。
I've had a few situations where I thought I was loading FireFox 3.6.x, but it was actually opening a newer version of Firefox (v16) installed on the machine. Because the profiles are stored in different places, it wasn't actually opening the profile I thought it was.
I thought I'd mention it just in case it explains varmyip's issue for other folks experiencing the same issue.