Unleashing Power of the D365 Regression Suite Automation Tool(RSAT)
- The Regression Suite Automation Tool (RSAT) allows users to create a set of automated tests by recording business tasks with the Finance and Operations task recorder, eliminating the need for writing source code. This tool dramatically reduces the effort and expenses associated with user acceptance testing while upgrading to a new version of Microsoft or implementing custom code and configurations in your Finance and Operations production environment.
- Additionally, RSAT integrates seamlessly with Azure DevOps for executing tests, generating reports, and investigating issues. Test parameters are separated from test steps and are managed using Microsoft Excel. In this article, we will explore the benefits of the D365 Regression Suite Automation Tool, how it works, and how it can help your business save time and money while improving the quality of your software products.
- Install the RSAT Desktop Application.
- Make sure Excel is installed on the machine.
- Get the Azure Access token.
- Get the Certificate from Lifecycle Services (LCS).
Users can download the RSAT Desktop application using the below link https://www.microsoft.com/download/details.aspx?id=57357
The users must have an Azure DevOps organization and generate a Personal Access token for the Azure DevOps organization to connect with RSAT.
To Generate the certificate file for the test tool, it is necessary to perform this action on the RSAT client computer that is running the tool. It is important to ensure that the certificate is generated on the same computer where the test tool is being executed.
To generate and edit test parameters, it is essential to have Microsoft Excel installed on your system.
Use Task Recorder to Capture Test Scenarios in D365 Finance & Operations with the D365 Regression Suite Automation Tool:
Task Recorder is a built-in automated task capture feature that seamlessly integrates with Dynamics 365 Finance and Operations. It allows users to effortlessly record every click and field value selection made during a process, providing the option to export the captured steps as a “Developer Recording XML Document.”
During the recording process in RSAT, users can generate reference variables by right-clicking on the desired field, selecting “Task Recorder,” and then clicking “Copy and Paste.” These reference variables are not visible in the recording itself but are recognized by RSAT. By performing this action, RSAT creates variables that can be utilized to link test cases together, forming a chain, once the parameter files are generated.
Users can set checkpoints by right-clicking on the desired field and selecting “Validate.” Next, they can choose the reference variable (previously copied variable) that enables a comparison between the actual and expected values. These reference variables play a crucial role in chaining the tasks within a test suite together.
Users have the flexibility to choose between different options during validation. They can select the “Current value” option to create a checkpoint and verify the value of the field. Alternatively, they can select the “Enabled” option to verify whether the field is enabled or disabled. Additionally, users can also verify if the field is in a read-only state, ensuring that it cannot be modified. These options provide comprehensive validation capabilities during the field validation process.
Users can download the recorded file by clicking on the save as Developer recording option, an XML file will be downloaded.
Attach the Developer Recording XML Document to the Test plan:
To facilitate effective RSAT automation, it is important to create comprehensive Test Plans and Test Suites. When adding Test Cases to these suites, it is recommended to give them titles that align with the names provided during the recording process. This ensures consistency and easy identification of the associated test scenarios. Furthermore, it is beneficial to attach the relevant
“Developer Recording XML Document” to each respective Test Case, enabling quick access to the recorded steps and enhancing test traceability.
Run the Test cases from RSAT:
Launch RSAT Application as a System Administrator and Configuring RSAT with Azure DevOps and D365 Application via the Settings Tab.
Load the Test Plan in the RSAT Tool after successfully configuring Azure DevOps.
Generate the execution and parameter files for your test cases in RSAT based on the attached “Developer Recording XML Document.” This process ensures that the recorded steps are translated into executable files, allowing for efficient and accurate test execution within the RSAT environment.
Launch the test plan in RSAT that you have prepared and configured. Initiate the execution of the test plan, allowing RSAT to run the specified test cases and scenarios. RSAT will automatically execute the test cases as per the defined sequence and parameters.
During the execution process, RSAT captures and records the test results, including any passed or failed tests, along with relevant details. Once the execution of the test plan is completed, RSAT proceeds to update the test results in Azure DevOps.
The test results, provide the execution status of each test case, and are synchronized and reflected in the corresponding Azure DevOps project or workspace. Navigate to the Azure DevOps platform to access the updated test results and review them in the context of your project’s testing activities.
The D365 Regression Suite Automation Tool is specifically designed for D365 applications and may not be compatible with other applications or systems. This limitation restricts its usability for organizations using diverse software ecosystems.
The tool supports only a single test plan at a time, which can be a drawback for organizations with complex testing requirements that involve multiple test plans simultaneously.
RSAT lacks the capability to execute multiple tests in parallel. This limitation can result in longer test execution times, especially for organizations with extensive test suites or time-critical testing needs.
Users are required to manually generate test execution files when installing a new version of the tool or when modifying or loading a new version of the recording file. This manual process can be time-consuming.
RSAT can only play back test steps that are recognized by the task recorder. Any test steps that fall outside its recognition scope, such as uploading files or performing page refreshes, cannot be accurately played back.
The tool does not support looping concepts within test scenarios. This limitation can be challenging for scenarios that require repetitive or iterative test execution.
RSAT lacks the ability to validate images as part of the testing process. This can be a drawback for organizations that heavily rely on image-based verification in their testing workflows.
The tool’s functionality and compatibility may depend on updates and releases from Microsoft. Organizations need to stay up-to-date with the latest versions and enhancements to ensure optimal performance.