retest.asiaStanding scope
The scope is written once and stays put. Amend it in writing whenever the product moves.
Retainers
The same test, every release.
Retests on a schedule you set, on the standing scope you signed. Open risks stay on the card until they move. Each card reads against the last.
The agreement
What a retainer holds.
A retainer is a standing scope and a schedule, both written down. Amendments go in writing too.
Retests on your schedule
We run the same four subjects every time, on the scope you signed. You set the cadence.
The comparison
Each card marks what moved since the last one. Open risks stay until they move.
A window in the schedule
Tell us the release date and we agree a test window for it, in writing, with the schedule.
A re-check after the fixes
Your team fixes what the card names. We retest what you fixed and mark it on the next card. Fix. Retest. Compare.
Fit
Who it fits.
A retainer suits a product that keeps moving. Here is where it fits.
- Teams shipping often
- Every release gets the same four subjects, so one card reads against the last. Nothing waits for a yearly review.
- A review is coming
- A questionnaire or a review is coming, and you want the list before it lands. If you need a certificate for an auditor, you need an accredited audit. A report card tells you what to fix. It does not certify you.
- An inherited codebase
- Nobody left notes, and you did not write it. The first card maps what is there. The next ones show what moved.
The sequence
How it starts.
The retests need a baseline to read against. One report card comes first.
- You start with one report card, so the retests have something to read against.
- We agree a standing scope in writing, and you sign the consent.
- You set the schedule, and we hold a test window around each release.
- Each retest lands within 72 hours as the same card, marked against the last one.
Retest Cybersecurity is a separate contract, with its own scope, timeline and consent. Fixing what we find is not included.
Ask
Ask about a retainer.
Send a URL and the release cadence you keep. The scope and quote come back in writing.
Send a URL, never credentials or secrets.