From no unit tests to 90 per cent coverage
A Dynamics and Power Platform team with no unit tests was taken from 0 to 90 per cent coverage.
What changed
The team had no unit tests. By the end of the engagement, unit test coverage stood at 90 per cent.
Why it matters
A team without tests finds out that a change has broken something when a user tells them. Every release becomes a risk, so releases get slower and rarer, and the system gets harder to change.
Tests turn that round. A change that breaks something fails within minutes, on the developer’s desk. Releases become routine.
The kind of work this is
This is what we mean by delivery put right: the environments, pipelines, branching, testing and release process that a Dynamics 365 or Power Platform team works within. The same discipline runs through everything we build ourselves.
Thirty developers moved to Git, and imports made three times faster
A team of thirty developers moved to Git source control, and solution import time was cut from two hours to 40 minutes.
From older CRMs to Dynamics 365, with fast CV search
Migrations from earlier Dynamics versions and other CRMs, with GDPR handling for candidate data, fast CV parsing, search, and candidate portals.
Start with a delivery health check.
One to two weeks on your Dynamics 365 or Power Platform estate, ending in a written report and a costed plan.