RSAT (Regression Suite Automation Tool ) implementation and configuration for Finance and Operations

Purpose

The Regression suite automation tool (RSAT) significantly reduces the time and cost of user acceptance testing.

This tool enables functional power users to record business tasks using the Finance and Operations Task recorder and convert these recordings into a suite of automated tests without the need to write source code. Test libraries are stored and distributed in Lifecycle Services (LCS) using the Business Process Modeler (BPM) libraries. These libraries are also fully integrated with Azure DevOps Services (Azure DevOps) for test execution, reporting and investigation. Test parameters are decoupled from test steps and stored in Microsoft Excel files.

Prerequisites

Dynamics 365 for Finance and Operations test environment (Demo or tier 2 UAT environment

Excel

Azure DevOps: You will need an Azure DevOps Test Manager or Test Plans license. For example, if you have a Visual Studio Enterprise subscription, you already have a license to Test Plans. Pricing-https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/
For a demo environment, you don’t need to buy any license.

Authentication Certificate: To enable secure authentication, RSAT requires a certificate to be installed on the RSAT client computer. The RSAT settings dialog box allows you to automatically create and install the authentication certificate.

Installation

Download Regression Suite Automation Tool.msi to your machine

RSAT requires Selenium and web browser driver libraries. RSAT will prompt you if needed libraries are missing and will automatically install them for you.

Configuration For RSAT

  1. Open RSAT application.
  2. Select the Settings button in the upper right to configure RSAT. And next steps will help you to find those required fields input.
  3. Go to project settings of Lcs for your projects.
    Go to Visual Studio Team Services. Here you need to mention the Azure DevOps project in the Azure DevOps site URL field. In order to do that, click on
    https://www.visualstudio.com
  4. Open Azure DevOps and create a new organization if there is not an existing one.
  5. Now create a new project as shown below
  6. Now you need to set up a security token by clicking on  account info>security

  7. Once you create the token, save it as you will not be able to access it again when you want to use it.
  8. Once that is done, go back to the main page and create a new test plan. Name it as RSAT-TT (or you can use any name)
  9. Now right click on RSAT-TT and create a new suite you can name it ‘Demo’. Azure DevOps setup is done.
  10. In Azure DevOps site URL mention Organization name that you set up in Azure DevOps. And in Personal access token field paste the token that you had earlier saved.
  11. Click on continue to select the project and continue, Save.
  12. Now you need to deploy it to the environment
  13. Next, open the Regression Suite Automation Tool, Go to settings in Azure Dev Ops Url field copy it from the LCS Access token should be the security token you had copied. Click on Test connection so the Project name and Test plan will populate.
  14. Now run VM. You will find Hostname and SOAP Hostname by going to IIS and then right-clicking on AOSService>Edit bindings. Copy both the Hostname and in Hostname and SOAP Hostname fields paste these values
  15. Admin username should be the username you use to login to your environment.
  16. To generate Thumbprint click on New and save at any location and then copy the generated certificate to the VM
  17. Open the copied certificate and install it to the local machine at personal and Trusted Root Certification Authorities locations.Now Open the wif file in admin mode in notepad from the given location of VM
    In wif file find CN name=127.0.0.1 exists or not.
    If not, copy the selected portion and paste it below the same authority block.

    Now add modify those lines as follows:

    <authority name=”CN=127.0.0.1″>

                <keys>

                  <add thumbprint=”F46D2F16C0FA0EEB5FD414AEC43962AF939BD89A”/>

                </keys>

                <validIssuers>

                <add name=”127.0.0.1″ />

                </validIssuers>

                </authority>

     ( Note: Add thumbprint of installed Certificate in wif as shown)

     


    Final steps include

    • Copy thumbprint from RSAT settings (which was generated when you click on New) and paste it in wif file in your VM
    • Then Mention the company name
    • And Working directory
    • Set default browser as internet explorer
    • Save as and ok
  18. Next, Go to LCS open business process modeler and create a new Library
  19. Name it as RSAT, go to edit and rename the process as required and you may add a child node to it by clicking on the Add process.
  20.  Now go to Finance and operations, go to test recorder
  21.  Create recording by clicking on create a recording and perform the operation and then click on the stop button. Name it as per your need then Save it to Lifecycle services or Save this to PC option. Click ok
  22. Now go back to LCS in the project library and click on the requirement, tab check it’s syncing
  23.  Now Sync test cases and VSTS sync
  24. Next, go to Visual studio DevOps, test cases, click on Add existing
  25. Then click on the run query and click on Add test case
  26.  Now go to regression suite automation and load the test and download test cases. select test and click on new and generate test execution parameter files
  27. Then click on edit option for the older version to edit values in excel
    For older version

    For newer version

    Now edit metadata for the test in excel file and save and close

    Now Run the test

    after this step, automatic session for the test is handled by selenium where the browser will perform steps as test cases
  28. Then run the test and after it’s completed successfully click on upload (Note the result as passed)

Share Story :

SEARCH :

FOLLOW CLOUDFRONTS BLOG :

FOLLOW CLOUDFRONTS BLOG :

Enter your email address to follow this blog and receive notifications of new posts by email.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close