Extension major-release regression
For ISV engineering leads · Plugs into your pipeline
Your extension has to prove against every Acumatica major, and the treadmill never slows down.
You get. Scenario suites per extension, executed against each release candidate as a gate in the build pipeline you already run — the same regression engine as tenant major-release regression, packaged for an ISV release cadence.
Pass/fail is not a substitute for your own release sign-off — liability language stays explicit.
I wire release certification scenarios the same way upgrade pilots run for VARs.
how it works
Same loop under every offer: version → rebuild → exercise → report.
Nothing installs inside Acumatica. Nothing for you to keep running.
- Demo without the afternoon rebuild
- Minutes, not a day: clean company, linked transactions already in it — same rebuild next week when the pitch goes sideways.
- See what is actually configured
- Live tenant extracted to Git; agreed config versus live, sandbox versus production — ranked lists, no writes.
- Catch breakage before production
- Business scenarios on an upgraded copy. Failures name the step — not a customer on the phone.
- Cutover becomes a rehearsal
- Rebuild, load, exercise, recon, tear down — repeat until go-live is boring and the controller has a trail.
Work product stays in your repo. Read-only work only reads; release and cutover never touch production until the SOW says so. Hosted tenants use what you already have; full rebuilds need a lab you control — every engagement states which — and your Acumatica version is pinned.