Error: "Stale Element Reference Exception"


Solution: This Error is caused due to 2 reasons:

  • The element has been deleted entirely.
  • The element is no longer attached to the DOM.


The second case is the most common cause. Page Elements are detached from the DOM during AJAX requests or Page reloads and reattach automatically once the function is executed. In this case, We just need to add a Wait of about 10 seconds using the "Wait for test data seconds" template as described below:

How to add a Wait in Test Cases?


Error: "Exception in initiating a browser session in path: timeouts"


Solution: This Error is most commonly caused when the browser session doesn't start in defined time and the request gets timed out i.e communication between Testsigma and Browser fails.

Most probable reason for this error is an outdated Selenium Browser driver may lead to this.


We can fix this by updating the drivers in the Apache Tomcat folder to latest version. Refer the below article for a detailed guide on updating the drivers folder in the Local Test Machine:

How to update Testsigma Agent Driver files on local machine?


Error: "A session with id ="<32_character_session_ID>" was not found "


Solution:

This Error is most commonly caused when the Web Browser session starts successfully but fails to communicate with Testsigma properly.


In Windows, this issue is usually caused due to outdated driver files. Refer the below article for a detailed guide on updating the drivers folder in the Local Test Machine.

How to update Testsigma Agent Driver files on local machine?


In Mac, this issue is usually caused due to missing WebDriver extension for safari or because the Allow Remote Automation option is not enabled. Refer the below article for a detailed guide on configuring Safari Browser in your Local Mac used as Test System:

Configuring Safari for Automated Tests in Testsigma


Error: "Exception in initiating a browser session in path:, The driver server has unexpectedly died!"


Solution:

This Error is most commonly caused when the Browser automation driver process(webdriverd) that communicates with the installed Browser is either unresponsive or dead.


Refer the below article for a detailed guide on killing unresponsive WebDriver and Safari Browser processes:

How to kill unresponsive WebDriver and Safari Browser processes?



Error: "Exception in initiating a browser session in path:, Could not create a session: The session timed out while connecting to a Safari instance"


Solution:

This Error is most commonly caused when the Safari Instance was initiated but there was some error in communicating with the Browser automation driver.


Refer the below article for a detailed guide on killing unresponsive WebDriver and Safari Browser processes:

How to kill unresponsive WebDriver and Safari Browser processes?


Error:  "Exception in initiating a browser session in path:, Could not create a session: The Safari instance is already paired with another WebDriver session.


Solution:

This Error is most commonly caused when an instance of Safari browser/ Webdriver process is already running and unresponsive.



Refer the below article for a detailed guide on killing unresponsive WebDriver and Safari Browser processes:

How to kill unresponsive WebDriver and Safari Browser processes?


Error:  "Element time out is timed out. Details: Expected condition failed: waiting for visibility of element located by <Locator>: <Locator_identifier>


Solution:

This Error is most commonly caused when Testsigma is unable to find the specified element on the loaded page.


There are two solutions for this issue. You can:

  • Either re-check the UI Identifier value for the Web Element or the Web Element is not visible on the loaded webpage.
  • Or If the Element is taking time to load, add a wait Test Step.


Refer the below article for a detailed guide on adding a wait Test Step to Test Cases:

How to add a Wait in Test Cases?


Error:  "Exception in initiating a browser session in path:, Could not create a session: You must enable the 'Allow Remote Automation' option in Safari's Develop menu to control Safari via WebDriver


Solution:

This Error is most commonly caused when Browser session fails to be initiated due to limited support from Safari browser.


Refer the below article for a detailed guide on configuring Safari for Automated Tests:

Configuring Safari for Automated Tests in Testsigma


Error:  "Exception in initiating a browser session in path:, For input string: ".DS_Store


Solution:

This Error is most commonly caused when Invalid files located in the File-system interfere with Testsigma operation.

Delete the unnecessary temporary and system files in driver folder such as ".DS_store" file or "Thumb.db" file.


Refer the below article for a detailed guide on fixing the DS Store Exception in your Mac machine:

Fixing the "Exception in initiating a browser session...DS_Store" issue in Mac


Error:  "Exception in initiating a browser session in path: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure." 


Solution:

This Error is most commonly caused when the selected Browser is not reachable or has incompatibility issues(beta or dev versions). Please try with the latest stable release version of the same Browser.