这是本节的多页打印视图。
点击此处打印.
返回本页常规视图.
理解常见的异常
如何处理Selenium代码中的各种问题.
无效选择器的异常 (Invalid Selector Exception)
某些时候难以获得正确的CSS以及XPath选择器。
潜在原因
您尝试使用的CSS或XPath选择器包含无效字符或无效查询。
可行方案
通过验证器服务运行选择器：
或者使用浏览器扩展程序来获取已知的良好值：
没有这样元素的异常 (No Such Element Exception)
在您尝试找到该元素的当前时刻无法定位元素。
潜在原因
- 您在错误的位置寻找元素 (也许以前的操作不成功)
- 您在错误的时间寻找元素 (该元素尚未显示在 DOM 中)
- 自您编写代码以来定位器已变更
可行方案
- 确保您位于期望的页面上，并且代码中的前置操作已正确完成
- 确保您使用的是正确的 等待策略
- 使用浏览器的devtools控制台更新定位器或使用浏览器扩展程序，例如:
过时元素引用的异常 (Stale Element Reference Exception)
当成功定位到元素时，
WebDriver会为其设置一个引用ID作为标记，
如果由于上下文环境发生变化，
导致之前元素的位置发生了变化或者无法找到了，
WebDriver并不会自动重新定位，
任何使用之前元素所做的操作将报错该异常。
常见因素
以下情况可能发生此异常:
- 您已刷新页面，或者页面的 DOM 已动态更改。
- 您已导航到其他页面。
- 您已切换到另一个窗口，或者进入/移出某个
frame / iframe。
常见方案
DOM已变更
当页面刷新或页面上的项目各处移动时，
页面上仍然有一个具有所需定位器的元素，
它只是不再被正在使用的元素对象访问，
并且必须重新定位该元素才能再次使用。
这往往通过以下两种方式之一完成：
每次使用时都要重新定位元素。
尽管有可能元素在定位和使用元素之间的微秒内，
发生变化的可能性很小。
缺点是这不是最有效的方法，
尤其是在 Remote Grid上运行时。
用另一个存储定位器的对象包装 Web 元素，并缓存定位的 Selenium 元素。
对该包装对象执行操作时，您可以尝试使用之前找到的缓存对象，
如果它是发生了变化，则可以捕获异常，
使用存储的定位器重新定位元素，并重试该方法。
这样效率更高，但如果您使用的定位器在页面更改后引用了不同的元素（而不是您想要的元素），则可能会导致问题。
上下文已变更
元素对象是针对特定的上下文存储的，
因此如果您切换到不同的上下文，
比如不同的 Window 或不同的 frame 或 iframe 元素引用仍然有效，
但暂时无法访问。在这种情况下，
重新定位元素无济于事，因为它在当前上下文中不存在。
要解决此问题，您需要确保在使用该元素之前切换回正确的上下文。
页面已变更
这种情况发生在您不仅更改了上下文，
而且导航到另一个页面并破坏了元素所在的上下文。
您无法仅从当前上下文重新定位它，
也无法切换回元素有效的活动上下文。
如果这是您的错误原因，
您必须回到正确的位置并重新定位元素。
无效 SessionId 异常
有时您尝试访问的会话与当前可用的会话不同。
可能原因
通常发生在会话被删除时（例如：driver.quit()）或会话发生更改时，例如最后一个标签页/浏览器已关闭（例如：driver.close()）。
可能的解决方案
检查脚本中是否有 driver.close() 和 driver.quit() 的实例，以及其他可能导致标签页/浏览器关闭的原因。可能是您在应该/能够定位元素之前就尝试定位了该元素。
1 - Unable to Locate Driver Error
Troubleshooting missing path to driver executable.
Historically, this is the most common error beginning Selenium users get
when trying to run code for the first time:
The path to the driver executable must
be set by the webdriver.chrome.driver system property;
for more information, see https://chromedriver.chromium.org/.
The latest version can be downloaded from https://chromedriver.chromium.org/downloads
The executable chromedriver needs to be available in the path.
The file geckodriver does not exist. The driver can be downloaded at https://github.com/mozilla/geckodriver/releases"
Unable to locate the chromedriver executable;
Likely cause
Through WebDriver, Selenium supports all major browsers.
In order to drive the requested browser, Selenium needs to
send commands to it via an executable driver.
This error means the necessary driver could not be
found by any of the means Selenium attempts to use.
Possible solutions
There are several ways to ensure Selenium gets the driver it needs.
Use the latest version of Selenium
As of Selenium 4.6, Selenium downloads the correct driver for you.
You shouldn’t need to do anything. If you are using the latest version
of Selenium and you are getting an error,
please turn on logging
and file a bug report with that information.
If you want to read more information about how Selenium manages driver downloads for you,
you can read about the Selenium Manager.
Use the PATH environment variable
This option first requires manually downloading the driver.
This is a flexible option to change location of drivers without having to update your code,
and will work on multiple machines without requiring that each machine put the
drivers in the same place.
You can either place the drivers in a directory that is already listed in PATH,
or you can place them in a directory and add it to PATH.
To see what directories are already on PATH, open a Terminal and execute:
If the location to your driver is not already in a directory listed,
you can add a new directory to PATH:
echo 'export PATH=$PATH:/path/to/driver' >> ~/.bash_profile
source ~/.bash_profile
You can test if it has been added correctly by checking the version of the driver:
To see what directories are already on PATH, open a Terminal and execute:
If the location to your driver is not already in a directory listed,
you can add a new directory to PATH:
echo 'export PATH=$PATH:/path/to/driver' >> ~/.zshenv
source ~/.zshenv
You can test if it has been added correctly by checking the version of the driver:
To see what directories are already on PATH, open a Command Prompt and execute:
If the location to your driver is not already in a directory listed,
you can add a new directory to PATH:
setx PATH "%PATH%;C:\WebDriver\bin"
You can test if it has been added correctly by checking the version of the driver:
chromedriver.exe --version
Specify the location of the driver
If you cannot upgrade to the latest version of Selenium, you
do not want Selenium to download drivers for you, and you can’t figure
out the environment variables, you can specify the location of the driver in the Service object.
You first need to download the desired driver,
then create an instance of the applicable Service class and
set the path.
Specifying the location in the code itself has the advantage of not needing
to figure out Environment Variables on your system, but has the drawback of
making the code less flexible.
Driver management libraries
Before Selenium managed drivers itself, other projects were created to
do so for you.
If you can’t use Selenium Manager because you are using
an older version of Selenium (please upgrade),
or need an advanced feature not yet implemented by Selenium Manager,
you might try one of these tools to keep your drivers automatically updated:
Download the driver
| 浏览器 | 支持的操作系统 | 维护者 | 下载 | 问题追溯 |
|---|
| Chromium/Chrome | Windows/macOS/Linux | Google | 下载 | Issues |
| Firefox | Windows/macOS/Linux | Mozilla | 下载 | Issues |
| Edge | Windows/macOS/Linux | Microsoft | 下载 | Issues |
| Internet Explorer | Windows | Selenium Project | 下载 | Issues |
| Safari | macOS High Sierra and newer | Apple | 内置 | Issues |
备注：Opera驱动不再适用于Selenium的最新功能，目前官方不支持。
