We build parameterized test scripts for your core business processes — the way your team actually works — then run them against every Microsoft preview and release. Video proof of every result.
Run Aged Accounts Receivable report— Report removed in 2025 release wave 1
—
✗
Verify report output matches expected
skipped
This failure was caught automatically after updating to 2025 release wave 1. The Aged Accounts Receivable report was removed by Microsoft — without automated testing, your team would have discovered this mid-process.
How it works
Build coverage → Run every wave → Get the report
You bring one hour per business process and a sandbox. We do the rest.
1
Build coverage
A one-hour discovery session per business process. You record yourself doing it once; we build and parameterize the scripts to match how your team works.
2
Run every wave
Scripts run against every Microsoft preview and release, and on demand after your own changes. We repair what Microsoft breaks.
3
Get the report
Pass/fail by scenario, step-level timing, video of every run. You know what broke before your users do.
Features
Stop hoping updates won’t break things
Purpose-built for the Business Central ecosystem — designed for how partners and IT teams actually work.
01
No code required
Scripts use BC’s built-in Page Scripting tool. Your functional consultants can read, run and maintain them — no developer needed.
02
See what went wrong
Every test run is recorded on video. Stop spending hours reproducing bugs — scrub to the exact moment of failure and see it happen.
03
Test everything in one click
Run every script against every connected company with a single click. Know in minutes — not days — if an update broke something.
04
Debug in seconds, not hours
Step-level logs with millisecond timing show exactly which action failed and why. No more guessing where things went wrong.
05
Track your testing confidence
Full run history shows pass/fail trends over time. Build a track record that proves your update process is solid.
06
Connect once, test everywhere
BC credentials are stored with enterprise-grade encryption. Set up your tenant connection once, then focus on the results.
Why it holds up
Built the way you actually work
A generic template tests Microsoft’s demo path. Your team creates a sales order from the Customer Card, not the Sales Orders list — so that’s the path we script. Scripts break when your process breaks, not when Microsoft’s demo data changes.
Build coverage once. Keep it validated every wave.
Two parts: a one-time Coverage Pack that builds your scripts, and an Update Validation subscription that keeps them working through every Microsoft release.
1 — Setup: Coverage Pack (one-time)
3 Processes
$2,995 one-time
Three business processes, scripted and parameterized
No setup fee. Upload and run unlimited Page Scripting scripts on the platform. You maintain them; repair is available at $350 per script. Subscription rates as below.
Every path includes it. Your scripts run against every Microsoft preview and release; we repair what Microsoft breaks in the processes we built.
$200/month per company
Billed annually · $2,400 total commitment
$240/month per company
Billed semiannually · $1,440 total commitment
A six-month term spans a full Microsoft release cycle, including preview validation. Twelve months covers both waves of the year at the lower rate.
Runs against every preview and release
Video of every run, step-level logs
Run history and pass/fail trends
Repair of scripts we built
Unlimited scripts on every plan
Priority email support
Example: 5 Processes + 12-month Update Validation = $4,295 today, then $200/month per company.
Questions
Frequently asked
Do I need a developer to use this?
No. Scripts are built with BC’s built-in Page Scripting tool — the same tool your functional consultants already know. We build and parameterize them; your team can read, run and extend them without code.
Is my data secure?
Yes. Credentials are encrypted at rest and in transit. We never store your business data — we only interact with your BC sandbox or tenant during test execution.
How long until we have coverage?
The delivery clock starts when your sandbox, master data and a named SME are ready. From there: one discovery hour per process, then we build, parameterize and run the baseline. Most 3- and 5-process packs are live within two to three weeks.
What happens when BC releases an update?
That’s exactly when you need us most. Your scripts run against the preview environment before the wave ships and again on release. Anything Microsoft breaks in the processes we built, we repair as part of Update Validation.
Ready to update with confidence?
The next BC wave is coming either way. Get coverage in place before it does.