MerivaneBook a demo

Vendor upgrade next month?Regression runs this week.

Quarterly vendor releases, security patches, browser updates. Merivane re-runs your approved OQ against the new version in UAT, logs the differences as defects, and gives you a signed regression report before go-live.

Book a demoWhere it sits in the chain
Where an upgrade enters the chain
  1. Approved requirement
  2. Test scripts
  3. Autonomous execution
  4. You take over
  5. Defects logged
  6. Signed OQ / PQ report
Regression

The full OQ, re-run on the new version.

Merivane runs the same approved OQ against the new version in UAT. Each step passes or fails against the same expected result, with new evidence.

  • Same scripts, new evidenceThe approved scripts do not change. The evidence is from the new version.
  • UI drift is flaggedA moved or changed control is handled, or handed to you.
  • You classify each differenceA difference becomes a test script update or a software defect, by your decision.
LIMS v12.3 → v12.496 steps
0/ 96 pass
DEF-044 · Approve button movedTest script update
Classify
DEF-045 · Audit entry missing user roleSoftware defect
Open
Cadence

Fits the vendor's release calendar.

Test in the vendor's sandbox or preview environment before the release date, so the regression report is ready by go-live.

  • Sandbox firstRun in the vendor's preview or sandbox before release day.
  • Runs on a scheduleSet to your release calendar.
  • Compare any two versionsNot only the version in production today.
Release cadenceTypical cycle
Release notes received
Impact scan
Regression run in sandbox
Defects triaged
Report signed
Go-live
Patches

Security patches without a validation debt.

A patch is a low-risk change with a targeted regression. Its evidence feeds the next periodic review.

  • Targeted regressionA patch runs a low-risk, targeted set of steps.
  • Feeds the periodic reviewPatch evidence carries into the next scheduled review.
  • Every version in the trailEach tested version is recorded, not only the latest.
Patch logLast 3 patches
Patch2026-08-02LIMS security patchPass
Patch2026-06-14Browser updatePass
Patch2026-04-29OS patchPass
Typical triggers

Events that start a regression run.

LIMS releaseQMS cloud releaseERP patchBrowser updateOS patchSSO change
Where this fits

Related pages in the chain.

Use caseChange management and re-validationMap a change to the requirements, scripts, and steps it affects.PlatformAutonomous executionIt runs the scripts. You watch every step.PlatformDefect managementA failed step becomes a defect, with evidence attached.

Questions about upgrades and patches.

If your question is not here, ask us. We reply within one working day.

How do we know the scripts still match the new screens?

The run tells you. A moved control is flagged and handed over, not guessed.

Can we test before the vendor's release date?

Yes, in the vendor's sandbox or preview environment.

Does the vendor's own validation package replace this?

No. You validate intended use in your configuration.

Do we need a full OQ each time?

Your risk assessment decides. Full or targeted.

Now onboarding validation pilot partners

See a full run on one of your systems.

Bring one approved requirement. We show you the chain end to end, on a system you already use, in under an hour.

Book a demo
Reply timeOne working day
FormatLive run, 45 minutes