Regression Suite Automation Tool
Dynamics 365 for Finance and Operations has evolved into purpose-built applications to help you manage specific business functions. For more information about these changes, see Dynamics 365 Licensing Guide.
The Regression suite automation tool (RSAT) significantly reduces the time and cost of user acceptance testing (UAT). UAT is typically required before you take a Microsoft application update, or before you apply custom code and configurations to your production environment. RSAT lets functional power users record business tasks by using Task recorder and then convert the recordings into a suite of automated tests, without having to write source code. For more information about Task recorder, see Task recorder resources.
RSAT is fully integrated with Microsoft Azure DevOps for test execution, reporting, and investigation. Test parameters are decoupled from test steps and stored in Microsoft Excel files.
RSAT usage is described in these topics:
- Regression Suite Automation Tool (this topic)
- Regression Suite Automation Tool installation and configuration
- Run Regression Suite Automation Tool test cases
- Validate expected values
- Chain test cases
- Derived test cases
- Regression Suite Automation Tool best practices
- Troubleshoot the Regression Suite Automation Tool
This tool is part of the end to end flow described below. The application, along with Microsoft Dynamics Lifecycle Services (LCS) and Azure DevOps, provide a set of tools for test case authoring (using Task recorder), configuration, execution, investigation, and reporting.
To learn more about this this process, see Create and automate user acceptance tests.
LCS and BPM
You aren't required to use the Business process modeler (BPM) tool in LCS. However, BPM is the recommended tool if you want to enable the management and distribution of test libraries across projects and tenants. These capabilities are especially useful for Microsoft partners and independent software vendors (ISVs). BPM enables the distribution of test libraries as part of LCS solutions.
If you are not using BPM, you can manually create test cases in Azure DevOps and attach developer recording files to your Azure DevOps test cases. You can create developer recording files directly from the Task recorder pane.
You must name the developer recording file Recording.xml before attaching it to the Azure DevOps test case. Alternatively, you can name the recording file -Test Case Title-.xml, where -Test Case Title- is the DevOps title of the test case.
Intended usage and test classification
Business cycle (business process) testing
The Regression suite automation tool is intended to be used for business cycle tests and scenario tests (multiple component tests) that usually occur at the end of the development lifecycle. This is also referred to as user acceptance testing. Business cycle testing consists of a smaller number of test cases than component or unit testing. This is illustrated in the following graphic.
Unit and component testing
For unit tests, we do not recommend that you use RSAT. Instead, use the SysTest framework and the build/test automation tools. For component tests, take advantage of the Acceptance test library resources (ATL). ATL is a library of X++ test helpers. When used with the SysTest framework, it offers the following benefits:
- Lets you create consistent test data.
- Increases the readability of test code.
- Provides improved discoverability of the methods that are used to create test data.
- Hides the complexity of setting up prerequisites.
- Supports high performance of test cases.
For more details, see Continuous delivery home page.
Data integration testing
Do not use RSAT for integration tests, instead rely on the data management framework (also known as DIXF). The Data task automation framework enables you to configure and automate the testing of your data integration scenarios.