Prepare your Dynamics 365 testing for RSAT retirement
If your Microsoft Dynamics 365 testing relies on the Regression Suite Automation Tool (RSAT), it's time to start planning your next steps. Microsoft has confirmed that RSAT will no longer be supported after 15 May 2027. Although the tool may continue to work beyond this date, organisations could face greater challenges maintaining reliable testing without ongoing support.
In this article, we outline our six-step approach to preparing for RSAT retirement. From assessing existing test coverage and evaluating alternatives to planning your migration, see how Columbus can help you build a reliable testing strategy that supports your business beyond the 2027 deadline.
Six steps to manage your Dynamics 365 RSAT transition
Moving away from RSAT requires careful planning to maintain test coverage and minimise disruption to your business. The following steps provide a practical framework for managing the transition.
1. Review your existing test coverage
Start by reviewing your existing test cases, test suites, data, dependencies and responsibilities. Look at how often tests are run, how much maintenance they require and where results are difficult to interpret. Map your tests against critical business processes such as sales orders, purchase orders, production and invoice posting, prioritising those most relevant to your operations.
Look beyond individual processes to identify gaps in coverage. Are important integrations being tested? Which activities still rely on manual checks? Involve both business and IT teams to understand where improvements are needed and build a clearer picture of your current testing approach.
2. Prioritise your testing requirements
Not every existing RSAT test needs to be migrated. Review your test scenarios and decide which should be migrated, redesigned, kept as manual tests or retired. Outdated or duplicate tests shouldn't receive the same attention as those supporting business-critical processes.
Prioritise your requirements based on business value, risk and available resources. Automation won't always be the right approach, particularly for infrequent activities or tests requiring human judgement. Decide whether to manage the transition in phases or as a single project, taking your testing requirements, release schedules and internal capacity into account.
3. Choose the right testing approach
Evaluate alternative testing tools against your business requirements and the processes you need to test. Consider how well each option supports Dynamics 365 Finance and Operations, connected applications, integrations and different testing environments. You should also assess how easy the tools are to use, maintain and manage with your existing team's skills.
Look beyond the initial investment to consider licensing, training, implementation and ongoing maintenance costs. Integration with Azure DevOps, reporting and test traceability may also be important, depending on your release processes. There’s no single approach that works for every organisation. The right choice should support both your immediate transition from RSAT and your longer-term testing strategy. For further guidance on evaluating your options, watch our webinar on RSAT retirement and choosing the right testing approach for Dynamics 365.
4. Test your approach before scaling
Before committing to a full migration, run a pilot using three to five business-critical testing scenarios. Choose realistic processes and data that reflect how your organisation operates. Agree on clear success criteria, including reliable results, manageable maintenance requirements and the ability to identify application issues.
Assess the time, resources and costs involved alongside the test results. Can your team understand failures, troubleshoot problems and maintain the tests without relying heavily on external support? Use the findings to decide whether the approach is suitable and identify any improvements needed before expanding your testing coverage.
5. Migrate while maintaining test coverage
Once you've selected your new testing approach, begin migrating tests based on your agreed priorities. Build and validate the replacement tests in stages, comparing results with your existing RSAT coverage to identify any gaps or inconsistencies. Continue running your existing RSAT tests during the transition until the replacement coverage has been validated.
Make training and knowledge transfer part of the migration process. Test owners should understand how to run tests, prepare data, investigate failures and maintain the new approach. Plan each migration phase around your business priorities, available resources and release commitments to minimise disruption.
6. Establish ongoing testing governance
Once your replacement testing approach has been validated and accepted, you can begin retiring RSAT from your testing processes. Keep relevant test assets and documentation for future reference, and establish clear responsibilities for maintaining tests, managing data, scheduling execution and resolving issues.
Agree on consistent standards for creating new tests, managing failures and reviewing results before releases. Clear governance helps your teams distinguish between testing errors and genuine application issues, supporting more informed release decisions. The aim is to establish a reliable, maintainable testing approach that continues to support your business as your Dynamics 365 environment changes.
