Why Your D365 Test Automation Strategy Needs a Rethink Before May 2027

If you’re running Microsoft Dynamics 365 and relying on RSAT (Regression Suite Automation Tool) to keep your test automation ticking, there’s a deadline you cannot afford to ignore: RSAT support ends on 15 May 2027. That’s not far away, and the decisions you make now will shape how painlessly your QA practice survives the transition.

So let’s talk about what comes next and why the answer is more interesting than you might expect.

The Quiet Problem with “Just Using Selenium”

When teams hear “we need to replace RSAT,” the instinct is often to reach for Selenium. It’s familiar, it’s been around forever, and it’s open source. But for D365 specifically, Selenium carries some stubborn baggage.

D365 forms are dynamic. Elements shift, iFrames nest inside each other, and Microsoft’s wave updates regularly reshuffle the DOM (Document Object Model). Selenium’s approach – manual waits, brittle XPath locators, means your tests break constantly. You end up with a team spending more time firefighting flaky tests than actually testing anything useful. And don’t even get started on MFA (Multi-Factor Authentication): Selenium simply struggles with repeated authentication prompts, which D365 throws at you relentlessly.

Selenium is a perfectly fine tool. It’s just not the right tool for this job.

Enter Playwright – Microsoft’s Own Answer

Here’s something that often surprises people: Playwright is built and maintained by Microsoft. That’s not a coincidence when you’re looking for an RSAT successor. It’s covered by Microsoft’s own D365 test-automation guidance, which means it’s designed with the exact environment you’re working in.

What makes it genuinely better for D365?

• Native auto-wait. Playwright waits for elements automatically. No more manually telling your tests to “wait a few seconds and hope the page is ready by then”. Playwright handles that intelligently on its own.
• Resilient locators. Instead of fragile XPath, Playwright uses role-based and ARIA locators that actually survive wave updates and nested DOM changes.
• Auth-state persistence. Set up your authenticated session once, and Playwright carries it forward. So no more MFA prompts derailing your test runs.
• Speed. Parallel execution out of the box, covering web and API, across multiple browsers.

And like Selenium, it’s completely free and open source. The difference is that it’s the lower-maintenance, D365-aligned choice.

Frameium: When “Good Enough” Isn’t Good Enough for the Enterprise

Playwright is a powerful engine. But a raw engine still needs a chassis, seats, and a steering wheel before you can drive it to work.

That’s where Frameium comes in – Testhouse’s enterprise layer built on top of Playwright specifically for D365 (and Salesforce) environments. It’s the difference between having a testing tool and having a governed automation framework.

A few things that make Frameium stand out:

Self-healing locators. Even with Playwright’s resilient selectors, Microsoft wave updates can still break things. Frameium auto-heals changed locators, so your test suite doesn’t become a maintenance burden every time Microsoft ships an update.

Pre-built D365 libraries. Instead of writing automation from scratch, teams start with ready-made assets for common D365 workflows. You’re automating from day one, not month three.

Reusable test assets. PDF validation, OCR, visual testing, database checks, Azure storage, MQTT – Frameium handles validations that go well beyond clicking buttons on a screen.

Triggerless, overnight automation. Unattended batch execution means your regression suite runs while your team sleeps. You come in the next morning to results, not a queue of manual tests.

Full DevOps integration. Jenkins, Azure DevOps, Jira, Zephyr, TestRail, Slack, Outlook –  Frameium plugs into the toolchain you already use, rather than demanding you build around it.

What Does This Actually Mean in Practice?

The numbers Testhouse puts behind Frameium are striking:

• 70% reduction in automation cycle time
• 30% lower script development cost
• Faster release cycles, faster developer feedback, faster everything

That’s not just a technology upgrade. That’s a meaningful shift in how quickly your organisation can ship with confidence.

The Clock Is Ticking

May 2027 might feel like it’s ages away. It isn’t. Migrating test automation is not a weekend project. Frameworks need to be built, teams need to be trained, existing test assets need to be ported, and the new suite needs to prove itself before you can retire the old one.

The organisations that start this conversation now will be the ones with a stable, governed, future-proof automation practice when the RSAT deadline arrives. The ones that wait will be scrambling.

Playwright gives you the right foundation. Frameium gives you the enterprise structure to scale it. And with RSAT’s clock running down, there has never been a better moment to make the move.

Interested in seeing what this looks like for your D365 environment? Testhouse builds, runs, and maintains it with you. Reach out at contact@testhouse.net or visit www.testhouse.net.