MerivaneBook a demo

A failed step becomes a defectbefore anyone writes it up.

When a step fails, a locked defect record is created with the evidence attached. It is linked to the step and the requirement, assigned, and tracked to closure. No re-typing into a tracker.

Book a demoWhere it sits in the chain
One chain, end to end
  1. Approved requirement
  2. Test scripts
  3. Autonomous execution
  4. You take over
  5. This pageDefects logged
  6. Signed OQ / PQ report
Creation

Created at the moment of failure, with the evidence attached.

A failed step does not wait for someone to notice. Merivane opens a defect record the moment the step fails, with the screenshots already linked.

  • Expected and observed, verbatimThe record shows exactly what the script expected and what the agent saw.
  • Evidence linked, not copiedThe screenshots and hashes stay in the audit trail. The defect points to them.
  • Locked at creationLater updates are appended. The original record does not change.
DEF-031 · Print certificateLocked
Step 6 · Print certificateCreated 2026-09-12 14:34 UTC
Expected
PDF download
Seen
Blank tab
Evidence
2 screenshots
Hash
1c5f…3e6a
Triage

Classify, assign, decide impact. Your call.

Merivane does not decide what a defect means. Your team classifies it, assigns it, and decides whether it affects requirement acceptance.

  • Impact is a signed decisionWhether a defect affects requirement acceptance is recorded and signed.
  • Rejections stay in the logA rejected defect keeps its reason on record. It is not deleted.
  • Assign to your team or the vendorOwnership is set per defect.
OQ-2214 · Defect log3 of 3 shown
DEF-031 · Print certificateVendor · High
Open
DEF-032 · Report footer dateConfiguration · Low
Closed
DEF-033 · Field label mismatchTest script error
Rejected
SoftwareConfigurationTest scriptDataEnvironment
Retest and closure

Closure needs a passing retest, not a comment.

A defect does not close on a note that it was fixed. It closes when a retest, with its own evidence, passes.

  • Retest is a new runIts own evidence, its own time stamp, linked to the original defect.
  • Closure is signedThe person who closes the defect signs the closure.
  • Reaches the reportThe defect log is section 3.0 of the OQ / PQ report.
DEF-031 · TimelineRetest and closure
  1. Created 14:34 UTCLocked, evidence attached
  2. Assigned to vendorOwner set by QA
  3. Fix reportedPatch applied in UAT
  4. Retest run OQ-2214-R1Step 6 · Pass
  5. Closed by Priya N.Closure signed
Defect classes

How your team classifies a defect at triage.

SoftwareConfigurationTest script errorDataEnvironmentDocumentation
Where this fits

Before and after a defect is logged.

BeforeAutonomous executionThe agent runs the script and stops when a step fails.BeforeEvidence and audit trailThe screenshot and hash a defect record points to.AfterE-signatures and complianceImpact assessment and closure are signed decisions.

Questions about defect management.

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

Does a failed step stop the run?

Your risk setting decides. A high-risk step pauses the run. A low-risk step continues.

Can we reject a defect as a test script error?

Yes. The rejection is recorded with its reason and stays in the log.

Does the defect log reach the report?

Yes. It is section 3.0 of the OQ / PQ report.

Can we push defects to Jira?

Under review.

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