Continuous service updates under Modern Lifecycle Policy and testing rigor using RSAT Regression Suite Automation Tool in Microsoft Dynamics 365 Finance and Operations One version

Continuous service updates under Modern Lifecycle Policy and testing rigor using RSAT Regression Suite Automation Tool in Microsoft Dynamics 365 Finance and Operations One version

MS D365FO online service is covered by Modern Lifecycle Policy which covers products and services that are serviced and supported continuously.

Microsoft will continually update Platform and Financial Reporting components with the option to postpone up to 2 consecutive service updates.

With continuous, touchless service updates in D365FO, it maintains backward compatibility, which means there is no need to ‘merge your code’. However the need to test all extensions as well out of box existing and new functionality is critical to ever evolve your cloud ERP.

After an update is completed in an environment, one needs to run all business processes to test and validate the update. Hence the need for continuous testing and to support this effort, a no-code automation test tool for business process testing is available, RSAT. 

RSAT allows us to record business tasks using the D365FO task recorder and convert them into a suite of automated tests. All this can be done without writing any code. RSAT is available in for use from PU15 and beyond.

This blog covers installation and configuration of RSAT tool to achieve touchless continuous service updates of your D365FO one version.

Sharing insights of configuring RSAT and its related components to be able to use it for continuous testing in below steps:

1) Ensure right project template is chosen in LCS project which comes from your DevOps project.

2) Ensure your LCS project has BPM library and it is sync with VSTS.

3) Next we would use D365FO task recorder and generate a AXTR file.

4) Next we either need to save directly to the BPM library from your D365FO task recorder or manually upload.

• In Lifecycle Services (LCS), in your project, on the BPM Business process libraries page, select the library to upload the task recording to.
• Click Author and edit and in the lines, locate and select the process to upload the task recording to. In the right pane, click Upload.

Note: Ensure in your test there is atleast one validation.

4) When this step is complete, your task recordings will become test cases in Azure DevOps and a link will appear under the Requirements tab.

5) Synchronize your BPM library with your Azure DevOps project.

On the Business process libraries page, on the tile for the library that you want to synchronize, select the ellipsis button (…), and then select Azure DevOps sync.

Note: Ensure first the VSTS sync is enabled and then sync up test cases as well.

This covers setup needed in LCS BPM and ensuring test cases using task recorder are created.

In next blog we would cover DevOps Test Manager and configuring RSAT