A Dedicated Test Manager for Your D365 Team

We embed as your dedicated test manager for Dynamics 365 F&O or Business Central — planning and running the manual testing your releases need. No automation platform to stand up and no permanent hire — just steady test coverage while your functional and technical leads stay focused on the release itself.

QA consultant reviewing a Dynamics 365 test checklist

D365 and ERP teams lose test coverage the same way every time: a release ships, the person who knew the test plan moves to another project, and nobody owns testing again until the next incident forces the question.

We fill that gap as a dedicated test manager — assessing what's actually covered today, planning manual test cycles around your releases and RSAT migration, and running them ourselves.

Signs You Need a Dedicated D365 Test Manager

No one owns testing between releases

Testing gets split across developers and functional consultants with their own priorities, so only the bare minimum gets covered.

Defects are reaching production

Issues a manual test pass would have caught surface after go-live instead, where they cost far more to fix.

We embed as your dedicated D365 test manager

You get the same one or two people who learn your Dynamics 365 environment, your release cadence, and your test history — not a rotating bench of unnamed testers.

0 1

We work inside your existing tools

We join your project and comms tools — Azure DevOps, Jira, Teams, Slack, whatever you already run — so test plans and defect reports live where your team already looks for them.

0 2

Tell us what needs to be tested

Walk us through the release, the RSAT migration, or the Business Central update, and we turn it into a manual test plan we execute ourselves.

0 3

We run the manual test cycles so your team doesn't have to

We execute the test cases, log the results, and keep the test plan current release over release — so your functional leads aren't the ones clicking through regression scripts the night before go-live.

0 4

The only failures you hear about are the ones pointing to real bugs

We triage every failed test case ourselves, separating real defects from environment noise before anything reaches your team.

0 5

TestSquad's Highlights

  • Direct contact, every time. You work directly with the people running your tests, not an account manager relaying messages from an offshore queue.
  • Manual testing, not tooling. We test D365 the way your users actually use it — working through screens and processes by hand — to catch what scripted automation is built to miss.

Software Testing Consulting Step by Step

We follow the same process on every engagement, whether it's a coverage assessment ahead of an RSAT migration or ongoing test management for a Business Central rollout.

Coverage assessment

We review what test cases already exist, walk through recent release notes and defect history, and talk to whoever currently owns testing.

Sample deliverables:
  • A coverage map showing which D365 processes have test cases today and where the gaps are.

Test plan for the release

We plan the manual test cycles around what's actually changing — a D365 F&O or Business Central release, an RSAT migration, or a new integration — and set a schedule and test cases against it.

Sample deliverables:
  • A test plan scoped to the release or migration
  • Manual test cases mapped to the processes and integrations affected
  • A schedule for test cycles against the release timeline

Manual test execution

We run the test cases ourselves, logging results and filing defects as we find them, and flag anything that needs your team's input before it blocks the release.

Sample deliverables:
  • Executed test cycles with pass/fail results
  • Defect reports triaged against the release

Knowledge handoff

When the engagement wraps, we hand off the test case library and coverage map so your team owns testing going forward, and we stay reachable if a question comes up after we're gone.

Sample deliverables:
  • The full test case library and coverage map

What This Delivers

Shorter software time-to-market
Reduced QA and testing costs
Minimized defects leakage
Streamlined collaboration and QA awareness within the project team
Manual test coverage that catches what automation misses
Optimized test coverage

QA KPIs we Track

  • Percentage of software requirements covered by test cases
  • Average and total number of created/updated test cases
  • Total number of executed test cases per certain period (e.g., iteration, build).
  • Average and total  number of found defects
  • Testing time and costs variance (the ratio between actual and estimated testing time and budget).
  • Defects leakage (percentage of issues found by software users or during user acceptance testing).
  • Severity of defects leaked into production.

QA KPIs will greatly depend on your QA maturity level, software and project specifics, QA process challenges you face. TestSquad provides a tailored set of KPIs, which you can use further during QA process self-assessments.

Book a Coverage Review

We'll walk your current test coverage with you and show you where the real gaps are. Name and email is all we need — we reply within one business day.

Get in touch directly

More about Software Testing