Test automation
Catch regressions before your users do. Automated tests that run on every change and against every Microsoft release, so update week stops being a gamble.
Contact Us
The problem automated testing solves
Business Central updates twice a year, and your extensions change more often than that. Without automated tests, the only way to know whether an update broke something is for a user to hit it, usually while doing something time-critical. Manual regression testing is the alternative, and it does not scale. Nobody re-tests every posting routine, every approval path and every report by hand before each release. What actually happens is that a subset gets checked, the rest is hoped for, and the gaps are found in production.
How we build the suite
We use Microsoft's AL test framework, so tests live in the same language and repository as the code they cover. Unit tests cover posting logic, calculations and validation rules. Integration tests cover the flows that cross module boundaries, which is where the expensive bugs live. Tests run automatically in a pipeline on every commit and on a schedule against Microsoft's preview builds. That last part is what turns the April and October releases from an event into a notification: you learn what breaks weeks before the update reaches your production tenant.
Where to start
You do not need full coverage, and chasing it is usually a waste. The return is concentrated in a small number of places: the routines that touch money, the customizations unique to your business, and the integrations where a silent failure means orders quietly stop arriving. We typically start with a focused suite over those areas, get it running in a pipeline, and extend it as the system changes. A suite that exists and runs is worth far more than a comprehensive one that was planned.
What you get
Microsoft's AL test framework
Tests live in the same language and repository as your extensions, not in a separate tool nobody maintains.
Unit tests on the money paths
Posting logic, calculations and validation rules, where a silent error is most expensive.
Integration tests across modules
The flows that cross boundaries, which is where the bugs that survive unit testing actually live.
Runs on every commit
Wired into Azure DevOps or GitHub Actions, so breakage is reported in minutes rather than discovered later.
Tested against Microsoft previews
Scheduled runs against preview builds, so you learn what an update breaks weeks before it reaches production.
Focused, not exhaustive
We target money paths, custom logic and integrations rather than chasing a coverage percentage that buys nothing.
Technologies
Frequently asked questions
Is test automation worth it for a small Business Central setup?
If you have custom extensions or integrations, usually yes, even a small suite. If you run close to standard with no customization, Microsoft already tests the base application and your return is much lower. We will tell you which situation you are in.
We already have customizations with no tests. Where do we start?
With the routines that touch money and the integrations that fail silently. A focused suite over those two areas catches most of what would otherwise reach production, and it can be built without pausing other work.
Do we need a CI/CD pipeline first?
Not strictly, but the value multiplies with one. Tests that run automatically on every change catch problems while the developer still has context. We set up Azure DevOps or GitHub Actions pipelines as part of the engagement where you do not have one.
Stop finding out about regressions from your users
Contact UsGet Free Estimation
Have a question or want to discuss a project? We'd love to hear from you. Get in touch and we'll respond as soon as possible.
Contact Information
Fill out the form and our team will get back to you within 24 hours.
Location
Serbia