Using RSAT for regression testing in a Tier-2 environment

We have been running an integrated pipeline for RSAT test for a while now but all of the testing has been focused towards stabilizing the tests and minimize noise and false positives. In doing this we have selected to run it against our SIT (OneBox) environment.

We have now decided to start testing for real in our UAT environment, which means that we need to redirect RSAT to connect to one of our Tier 2 environments instead. We will still use the SIT environment as a RSAT client but with an alternate configuration. This is a short step-by-step guide on how to create the new configuration.

  1. Log into the RSAT client computer and start RSAT
  2. Change the URL and SOAP URL to the:

  3. In LCS go to the UAT environment and export the RSAT Certificate. Remember to save the export password.
  4. Upload the file and extract it on the RSAT client machine
  5. Install the cer file to Local Machine – Trusted Root Certificate Authorities
  6. Import the .pfx file (using the password above) to the local machine

    more details are here:
  7. In RSAT – Setting change the certificate thumbprint to the one for your Tier 2 environment.
  8. In order to use the new config but still be able to test against the SIT enviroenment, click Save As at the top of the page ang save the new configuration to a file. You can now manually switch between the two configurations and also use the different files in build and deploy pipelines.

    That is all for today… Good Luck and happy testing 🙂

Regression suite automation tool installation and configuration – Finance & Operations | Dynamics 365 | Microsoft Docs
Troubleshoot the Regression suite automation tool – Finance & Operations | Dynamics 365 | Microsoft Docs

RSAT: Failed to download or overwrite attachment files – Some files maybe in use.

I had an issue today with one of my testcases in RSAT. When running it manyally from the RSAT UI it worked but when trying to run it from a PowerShell script I got this error:

Failed to download or overwrite attachment files – Some files maybe in use.

For some reason the test case uploaded duplicate files to Azure DevOps. When I ran the test in RSAT it uses the local file generated from RSAT and everything worked but when I ran it from the console it downloaded the files from DevOps, got the duplicates and for some reason failed.

The solution was to permanently delete the test case from DevOps and resync it from BPM.

Beware that that will give it another ID which will change the order of the tests.

Regression Suite Automation Tool: System.Exception: Microsoft (R) Visual C# Compiler version 4.6.1586.0 for C# 5

I had a really annoying issue today…

We are starting use Regression Suite Automation Tool (RSAT) for test automation in Dynamics 365 for Operations. This tool is using Task Recorder, Business Process Modeller and Azure Devops for automatically testing process in D365FO.

I needed to install it for one of my colleagues and run into this error message when I was trying to regenerate test files for a test case:

[BITS D365 RSAT] Create party record (external)
System.Exception: An error occurred while generating test cases. See details below. —> System.Exception: Microsoft (R) Visual C# Compiler version 4.6.1586.0
for C# 5
Copyright (C) Microsoft Corporation. All rights reserved.
This compiler is provided as part of the Microsoft (R) .NET Framework, but only supports language versions up to C# 5, which is no longer the latest version. For compilers that support newer versions of the C# programming language, see

c:\Temp\XXXX\MyTestCase.cs(253,56): error CS0266: Cannot implicitly convert type ‘Microsoft.Dynamics.TestTools.Dispatcher.Client.DispatchedForm’ to ‘MS.Dynamics.TestTools.DispatcherProxyLibrary.MyForm.MyGrid’. An explicit conversion exists (are you missing a cast?)

— End of inner exception stack trace —

My thoughts was that there was something wrong with my Dynamics 365 FO VM and I could not get it to work… after several frustrating hours I read a Yammer post that indicated that it might be an issue with the actual test case… go figure I had been testing with the same test case every single time. Once I switched test case everything worked… That is great… Wohoo

That is it for today