Skip to content

Commit ecc78c0

Browse files
[deploy site] added 3 exceptions in error doc
1 parent cb0bfc2 commit ecc78c0

1 file changed

Lines changed: 55 additions & 0 deletions

File tree

  • website_and_docs/content/documentation/webdriver/troubleshooting/errors

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.en.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -197,3 +197,58 @@ This can occur in several situations:
197197
This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following:
198198
using an explicit wait, or interacting with the page in such a way to make the element visible
199199
(scrolling, clicking a button, etc.)
200+
201+
## NoSuchAlertException
202+
An attempt was made to operate on a modal dialog when one was not open.
203+
204+
### Likely Cause
205+
206+
* Trying to interact with alert that hasn't appeared yet
207+
* Alert was already handled or dismissed
208+
* Alert appears asynchronously after certain actions
209+
* Timing issues where alert is expected but not yet present
210+
211+
## Possible Solutions
212+
213+
* Use explicit waits for alert presence: WebDriverWait(driver, 10).until(EC.alert_is_present())
214+
* Check if alert is actually present before interaction
215+
* Handle timing issues with alert appearance by adding appropriate delays
216+
* Verify the action that should trigger the alert is actually executed before attempting to handle it
217+
218+
## NoSuchElementException
219+
An element could not be located on the page using the given search parameters.
220+
221+
### Likely Cause
222+
223+
* The element is not present in the DOM when the locator attempts to find it
224+
* Incorrect selector or locator strategy being used
225+
* Element appears after page load due to dynamic content or JavaScript
226+
* Element is located in a different frame or window context
227+
* Timing issues where element loads after the search is performed
228+
229+
### Possible Solutions
230+
231+
* Use explicit waits to ensure element is present before interaction: WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.ID, "element-id")))
232+
* Verify the locator is correct by testing it in browser developer tools
233+
* Check if element is in a different frame and switch context if needed
234+
* Wait for dynamic content to load before searching for the element
235+
* Use more robust locator strategies (ID, CSS selectors, XPath)
236+
237+
## NoSuchFrameException
238+
A command to switch to a frame could not be satisfied because the frame could not be found.
239+
240+
### Likely Cause
241+
242+
* Frame doesn't exist or was removed from DOM
243+
* Incorrect frame identifier (name, id, or index)
244+
* Frame not yet loaded when attempting to switch
245+
* Using wrong frame reference (outdated index or incorrect name)
246+
* Frame is nested and requires switching to parent frame first
247+
248+
### Possible Solutions
249+
250+
* Verify frame exists using browser developer tools
251+
* Use correct frame identifier (name, id, or WebElement reference)
252+
* Wait for frame to be available: WebDriverWait(driver, 10).until(EC.frame_to_be_available_and_switch_to_it("frame-name"))
253+
* Check frame hierarchy and switch to parent frames in correct order for nested frames
254+
* Use frame WebElement instead of name/id: driver.switch_to.frame(driver.find_element(By.TAG_NAME, "iframe"))

0 commit comments

Comments
 (0)