Install and update
Install the extension from the Chrome Web Store. Chrome 123 or newer.
Install
Section titled “Install”-
Open Testomat.io in the Chrome Web Store and click Add to Chrome, then Add extension.
-
Click the puzzle icon in Chrome’s toolbar and pin Testomat.io with the pushpin:

-
Click the pinned icon — the panel opens and asks you to connect (Connect to Testomat.io). That is the next page: Connect.
Update
Section titled “Update”Chrome updates the extension by itself. Your token, settings and unsent results survive an update.
If it didn’t work
Section titled “If it didn’t work”- Chrome refuses to add it — check your Chrome is 123 or newer
(
chrome://settings/help).
Install from source
Section titled “Install from source”For developers: run the code from this repository instead of the store copy.
The source copy has the same ID as the store copy, so Chrome holds only one of
them: remove the store copy on chrome://extensions first. Removing it
deletes its token and settings, so you connect again.
-
Get the folder — either way works:
-
download the newest
testomat-io-<version>.zipfrom Releases — the file under Assets without-webstorein its name (that one is the Chrome Web Store upload) — and unpack it, or
-
git clone https://github.com/testomatio/browser-extension.git
-
-
Open
chrome://extensionsand switch on Developer mode (top right). -
Click Load unpacked:

…and pick the folder:
- from the zip — the folder you unpacked;
- from the clone — the
extension/folder inside it, not the repository root.
Either way, the right folder is the one with
manifest.jsondirectly inside. -
Pin the icon and connect, as in steps 2–3 of Install.
There is nothing to build or install beyond that — the folder runs as is.
Update a source copy
Section titled “Update a source copy”A source copy does not update itself. To get a new version:
-
Replace the folder contents: unpack a newer zip over the same folder, or
git pullin the clone. -
On
chrome://extensions, press the reload (↻) icon on the Testomat.io card:
Your token, settings and unsent results survive the reload.
If a source copy didn’t work
Section titled “If a source copy didn’t work”- “Load unpacked” is missing — Developer mode is off; the switch is in
the top right corner of
chrome://extensions. - “Manifest file is missing or unreadable” — you picked the repository
root; pick the
extension/folder inside it. - Updated, but behaves like the old version — press reload (↻) on the extension’s card; replacing the files alone is not enough.