Manage Plugins
Install, update, remove, and configure plugins in the TestVibe Plugins marketplace.
The Plugins view shows a searchable catalog on the left — with category filters and an Installed shortcut — and plugin cards on the right. Each card shows the publisher, version, download count, a short description, and an install or installed state.
Install Or Remove A Plugin
Select Plugins from the navigation rail.
Search or pick a category to find the plugin.
Select Install on the card. Installed plugins show an Installed badge; select it to remove or update.
Once installed, the plugin's steps are available in every feature — write them in Gherkin like any other step.
Installing (or removing) a plugin persists immediately for the project — it stays installed after you navigate away, reload the page, or come back later, and every teammate on the project sees the same state. If a card ever looks wrong right after a toggle, use the catalog's Retry option to refresh from the server rather than assuming the toggle didn't save.
Configure Required Values
Plugins that need secrets or variables list them in a Requires section in the plugin's detail modal. Each requirement shows a Set or Not set badge, and the header counts how many are still missing.
You can fill a value inline — type it into the requirement's field and it saves to the project's Variables & Secrets (secret values are write-only). Or select Manage / Settings → Variables & Secrets to set them on the dedicated panel. Reference them from steps with {{secret:NAME}} and {{var:NAME}}.
Visual Comparison Plugins: Visual Regression And TestVibe Assistant
Two catalog plugins compare screenshots against a saved baseline, but they check different things. You can install and use either or both in the same project.
How it compares
Pixel-diff — an exact, deterministic pixel comparison against the baseline image.
AI vision — your project's AI model looks at the live screenshot and the baseline and judges whether they match the described intent.
Best for
Catching any unintended visual change, down to the pixel.
Comparisons that should tolerate minor rendering noise (fonts, dates, dynamic content) but still catch a meaningfully different page.
Where the baseline lives
Your project's Asset Library, under the reserved visual-baselines/ folder — it shows up as a normal asset in Settings → Project → Assets.
Any image you've stored in the Asset Library, referenced from the step.
Cost
No AI usage — pixel comparison only.
Metered like other AI calls (AI tokens).
How Visual Regression establishes and checks a baseline:
The first time a step compares a named snapshot, there is no baseline yet — TestVibe saves that screenshot as the baseline in the Asset Library and passes.
On every later run, the step downloads the saved baseline and pixel-diffs it against the current screenshot.
If the difference is within threshold, the step passes silently — a green run's evidence never includes a diff image.
If the difference exceeds the threshold, the step fails and TestVibe writes expected, actual, and diff images to that step's artifacts, so you can see exactly what changed.
Accepting a new look on purpose: there's no separate "approve" button. Delete the baseline asset under visual-baselines/ in Settings → Project → Assets, then run again — the next run re-establishes a fresh baseline from the current page.
TestVibe Assistant's compare_screenshots works the same way from the Gherkin author's side — reference a baseline asset and a threshold — but instead of a pixel diff, it sends both images to your configured AI model and returns a pass/fail judgment plus a written summary of what differs. Use it when small, expected rendering differences would otherwise cause false failures in a strict pixel diff.
Tips
Install only what the project uses — every installed plugin's keywords show up in authoring suggestions.
When a plugin step fails with a missing-value error, check Settings → Variables & Secrets first.
Use Publish plugin (the upload button in the rail) to share internal helpers with your team.
Related Help
Last updated
Was this helpful?