- NLPs
Retrieve Value in Text Element
Capture Dropdown Elements
Unable to Select Radiobutton
Unable to Click Checkbox
Clearing the Session or Cookies
UI Identifier NLP
Drag & Drop NLP
Uploading Files NLP
Use MySQL Addon in NLPs- setup
Server Docker Deployment Errors
Secured Business Application Support
Troubleshooting Restricted Access to Testsigma
Why mobile device not displayed in Testsigma Mobile Test Recorder?
Unable to Create New Test Session
Agent Startup Failure Due to Used Ports
Tests Permanently Queued in Local Executions
Fix Testsigma Agent Registration Failures
Testsigma Agent Cleanup
Need of Apache Tomcat for Testsigma Agent- web apps
URL not accessible
Test Queued for a Long Time
Issues with UI Identifiers
Missing Elements in Recorder
Collecting HAR File
Errors with Browser Session
Page Loading Issues- mobile apps
Failed to Start Mobile Test Recorder
Troubleshooting “Failed to perform action Mobile Test Recorder” error
Why Test Execution State is Queued for a Long Time?
Why Mobile App Keeps Stopping After Successful Launch?
More pre-requisite settings
Why am I not able to start WDA Process on iPhone?
What are the Most Common causes for Click/Tap NLP Failure?
How to Find App Package & Activity in Android?
Cross-environment Compatible ID Locators (Android)
Why Accessibility IDs Over other Locators?
What are Common Android Issues & Proposed Solutions?
How to Find the App Bundle ID for iOS?
Developer Mode (iOS 16 & Above)
How to Handle iOS App Compatibility Issues?
How to Disable Play Protect for SMS Forwarder Installation?
How to Capture Network Logs in an Android Application?
Automating Chrome Extension in Testsigma
You can automate the Chrome extension in Testsigma using two methods:
- Hybrid Execution: Run on the Chrome browser installed on your local machine.
- Cloud Execution: Run on the Chrome browser in Testsigma Lab, SauceLabs, or Browserstack.
This article discusses setting up and running automated Chrome extension tests in Hybrid & Testsigma Lab environments.
Automating a Chrome Extension
A Chrome extension improves the browser's capabilities. Add extensions from the Chrome Web Store or search for the extension to find the store link.
Create a CRX File
- Go to CRX Viewer.
- Select Open in this viewer.

- Choose CRX and download the file (This file is necessary for automation).

- Searching for .html?$ and find files like panel.html and popup.html. The popup.html file is usually the target for automation.
- Go to chrome://extensions/ and access the popup.html file.
- Locate the plugin you wish to automate and access its unique ID.
- In this case unique ID is epmomlhdjfgdobefcpocockpjihaabdp.
Hybrid Mode: Local Test Execution
- Setup and start Testsigma Agent. For more information, refer to the documentation on setting up Testsigma Agent.
- Place the CRX file to your Testsigma Agent folder.
-
Specify the Extensions path in the Desired Capabilities.
Name Data Type Value goog:chromeOptions String {"extensions":["extension.crx"]}
You can also add multiple extensions, with this format for Values: {"extensions":["extension1.crx"],["extension2.crx"]}.
When the test execution starts, the desired capabilities will install the extension automatically. You can verify the installation by checking for the extension icon in the browser's top-right corner.
With Chrome version 137, Google has disabled the use of command-line switches like --load-extension in stable builds to improve security and stability. Instead, you can configure the following in Desired Capabilities:
| Name | Data Type | Value |
|---|---|---|
| goog:chromeOptions | String | {"args":["--disable-features=DisableLoadExtensionCommandLineSwitch"]} |
| goog:chromeOptions | String | {"args":["--load-extension=Place the file path here"]} |
Steps to Get the Extension Path
- Go to the Chrome Web Store and search for the Chrome extension source viewer extension.
- Click Add to Chrome to install the extension.
- Once added, go back to the Chrome Web Store.
- While viewing the Chrome extension source viewer extension’s page, click the Chrome extension source viewer extension in your browser toolbar.
- Select Download as ZIP from the available options.
- Extract the zip file and copy the file path along with the file name.
{"args":["--load-extension=Place the file path here"]}
When copying a file path on Windows, it appears like this: C:\testing\downloads\extension. However, in the Desired Capabilities, you must escape backslashes like this: C:\\testing\\downloads\\extension.
Hybrid Mode: Cloud Test Execution
Repeat the same Desired Capabilities we have discussed in the above section before executing the test plan.