From approved requirementto scripts you can approve.
Upload an approved URS, FRS, or change request as PDF or Word. Merivane parses the requirements, proposes a risk level for each, and writes scripts with every step, expected result, and acceptance criterion. Edit any step. Approve to lock.
- Approved requirement
- This pageTest scripts
- Autonomous execution
- You take over
- Defects logged
- Signed OQ / PQ report
It reads the requirement the way a validator does.
Merivane reads the approved document line by line. It proposes a risk level for each requirement it finds and flags any line that is not clear.
- One requirement per lineEach line keeps a reference to its source page.
- Unclear text is flaggedAmbiguous wording is flagged, not guessed.
- Risk is proposed, with a reasonEach proposed level carries a one-line rationale.
A QA approver approves the batch record after review.
The approver identity and time are recorded.
Approval is blocked until the review field is complete.
A certificate is generated on approval.
The next step owner should be notified.
Every step has an expected result.
Every script carries its requirement ID, each step, the expected result, and the acceptance criterion. Test depth follows the risk level you approve.
- Steps, results, criteriaEvery step has an expected result and an acceptance criterion.
- Depth follows riskTest depth follows the risk level, under GAMP 5 or CSA.
- Traced to its requirementEvery script carries its requirement ID.
| Step | Action | Expected result | |
|---|---|---|---|
| 1 | Log in as QA-02 | Dashboard opens, role shows QA | High risk |
| 2 | Open batch record BR-2219 | Record opens in review state | High risk |
| 3 | Enter sample result 4.2 mg | Value saved, audit entry created | Medium |
| 4 | Approve record | Status changes to Approved | High risk |
| 5 | Verify audit entry | Entry lists user, time, meaning | High risk |
You edit. You approve. It locks.
Edit any step before you approve it. Approval locks the script and is recorded as a signed event.
- Edit in placeChange any step before you approve it.
- Approval is signedApproval is a signed event, not a status change.
- Revisions keptA changed requirement creates a new script revision. The old one stays.
URS, FRS, configuration specification, change request, user stories, SOP extract.
What happens after the scripts are locked.
Questions about test scripts.
If your question is not here, ask us. We reply within one working day.
Does it write unscripted tests?
No. It writes scripted tests for the risk levels you set. Unscripted sessions are done by people. See computer software assurance.
How does it decide risk?
It proposes a level. You decide. The rationale is recorded.
What if the requirement is not clear?
It flags the line and asks. It does not invent a step.
Can we use our own script template?
This is under review.
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