Built by someone who’s been there

If you work with Business Central, you know the drill. Microsoft ships an update. An ISV pushes a new version. A developer deploys a fix for accounting. Someone tightens a setup. Each time, somebody should click through the business processes to make sure nothing else broke — creating customers, posting sales orders, running reports — and usually nobody does, because it takes days. The break shows up later, somewhere nobody was looking, and the users find it first.

I watched it happen with Business Central 25. The wave added a Sustainability feature with new tables, and posting routines started touching them. In the same week, several of my clients hit errors — the first on table 6217, Sustainability Setup — in business processes that had nothing to do with sustainability. Their users found out first. That week is why BusinessCentralTesting exists.

BusinessCentralTesting exists to end that cycle. We build the scripts for your core business processes, give you one click to run them in a sandbox before every change goes into production — Microsoft’s, your ISVs’, your own — record video of every step, and tell you exactly what broke — so you can fix it before your users ever notice.

We’re not a generic testing framework trying to bolt on BC support. Every feature is designed specifically for the Business Central ecosystem, using BC’s own Page Scripting tool so your functional consultants can read and run tests without writing code. Behind it is 25 years of NAV and Business Central implementations across manufacturing, distribution and financial operations.