While executing Test Cases in Testsigma, we may come across certain issues which may be caused due to an incorrect configuration, invalid user input or in rare cases, Application bugs.


Following are some of the common error codes and ways to fix them:


Error Message
Error Type
Reason
Solution
Operating System
Driver/Browser initiation Issues
Exception in initiating a browser session in path: timeouts
Hybrid Execution Initiation Error: Outdated drivers
The browser session was not started in defined time and the request was timed out i.e communication between Testsigma and Browser failed.

This may be caused due to an outdated Selenium jar file.
Update the drivers folder.

More details:
How to update Testsigma Agent Driver files on local machine?
All
A session with id ="<32_character_session_ID>" was not found.
Hybrid Execution Initiation Error: Outdated drivers
The Web Browser session was started successfully but couldn't communicate with Testsigma properly.

In Mac, this issue is usually caused due to missing Webdriver extension for safari or because the Allow Remote Automation option is not enabled.
In Windows/Linux,
Update the drivers folder.

More details:
How to update Testsigma Agent Driver files on local machine?
Windows
In Mac, Enable the "Allow Remote Automation" option in Safari settings.

More details:
Configuring Safari for Automated Tests in Testsigma
Mac
Exception in initiating a browser session in path:, The driver server has unexpectedly died!
Hybrid Execution Initiation Error : Unresponsive DriverThe Browser automation driver process(webdriverd) that communicates with the installed Browser is either unreponsive or dead.1. End the Execution.
2. Close Safari browser.
3. Kill the unresponsive WebDriver process.
4. Restart the Execution again.

More details:
How to kill unresponsive WebDriver and Safari Browser processes?
Mac
Exception in initiating a browser session in path:, Could not create a session: The session timed out while connecting to a Safari instance.
Hybrid Execution Initiation Error: Unresponsive Webdriver process
Safari Instance was initiated but there was some error in communicating with the Browser automation driver
1. End the Execution.
2. Close Safari browser.
3. Kill the unresponsive WebDriver process.
4. Restart the Execution again.

More details:
How to kill unresponsive WebDriver and Safari Browser processes?
Mac
Exception in initiating a browser session in path:, Could not create a session: The Safari instance is already paired with another WebDriver session.
Hybrid Execution Initiation Error: Unresponsive Webdriver process
An instance of Safari browser/ Webdriver process is already running and unresponsive.1. End the Execution.
2. Close Safari browser.
3. Kill the unresponsive WebDriver process.
4. Restart the Execution again.

More details:
How to kill unresponsive WebDriver and Safari Browser processes?
Mac





User Errors
Element time out is timed out. Details: Expected condition failed: waiting for visibility of element located by <Locator>: <Locator_identifier>
Element not found Error
Testsigma couldn't find the specified element on the loaded page.
Re-check the UI Identifier value for the Web Element or the Web Element is not visible on the loaded webpage.

If the Element is taking time to load, add a wait Test Step.

More details:
How to add a Wait in Test Cases?
All
Execution Environment errors

"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."


Execution Initiation Error: Mac/Safari issue
Browser session could not be initiated due to limited support from Safari browser.
Enable the "Allow Remote Automation" option in Safari settings and check Safari WebDriver is present.

More details:
Configuring Safari for Automated Tests in Testsigma
Mac

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


Execution Initiation Error: Mac issue
Invalid files located in the filesystem interfere with Testsigma operation.
Delete the unnecessary temporary and system files in driver folder such as ".DS_store" file or "Thumb.db" file.

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

"Exception in initiating a browser session in path:, An unknown server-side error occurred while processing the command. Original Error: Cannot start <application_name> application


Original Error: The permission to start <activity_name> activity has been denied. Make sure activity/package names are correct.The package name or activity name is not correct

OR

A user doesn't have permission to start the Activity due to missing permissions in the manifest.
Double check the Activity and package name or try another activity name.Android Native





Others
Prerequisite Failed
Execution Error
The Test Case selected for Execution has another Test Case as a prerequisite requirement.
Add the Prerequisite Test Case to the Execution
All


Note: The table will be updated if we find more error codes. Your support is highly appreciated in finding new errors. Please report if you face any error other than the ones given above.