Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (2023)

  • Article
  • 8 minutes to read

You can use Task recorder and Business process modeler (BPM) to create user acceptance test libraries. Task recorder is a powerful tool to record test cases and organize them by business process using BPM. As a Microsoft partner you can use BPM to distribute test libraries to your customers via LCS and LCS solutions. If you are a customer, use BPM to author and distribute test libraries across different projects and team.

Because BPM can be synchronized with Azure DevOps (formerly known as Visual Studio Team Services), you can automatically create test cases (including test steps) in your Azure DevOps project. Azure DevOps can then serve as your test configuration and test management tool where you can create targeted test plans and test suites, manage the execution of tests and investigate results. For more information about testing with Azure DevOps, see What are test plans, test suites, and test cases?

This article walks through the process of creating and executing acceptance test suites to be used for manual or automated testing.

Create a Scenario Acceptance Testing BPM library

BPM is a great LCS tool to describe a hierarchy of business processes and user tasks. LCS also allows Microsoft partners and customers to author and distribute BPM libraries across LCS projects via the Asset library. This section describes how to take advantage of BPM to define your acceptance test library.

Create a BPM library

There are several ways to create a Business process modeler (BPM) library. For more information about how to create libraries in BPM, see Create, edit, and browse Business process modeler (BPM) libraries.

For illustration purposes, this article uses a library that contains common business processes, such as create an expense report and approve order requests. The library was created by using the Excel import functionality.

Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (1)

Record test cases and save to BPM

After you have created a BPM library, you'll need to use Task recorder to create your test cases and then upload the cases to BPM. There are several ways to do this.

If you're using a BPM library that already has all of the necessary task recordings (test cases) attached, you can skip this step. Otherwise, follow the instructions below to create new task recordings.

Create and save a new task recording

  1. Open the client and sign in.

  2. Select the company that you want to use while recording.

    (Video) Dynamics 365 Finance, SCM Acceptance Test Library

  3. Go to Settings > Task recorder.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (2)

  4. Click Create a new recording.

  5. Enter a name for the recording, and then click Start. Recording begins the moment that you click Start.

  6. When the recording is complete, in the Task recorder pane, click Stop.

  7. To save the task recording to an attached BPM, click Save to Lifecycle Services.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (3)

  8. Select the library that you want to save the recording to, and then click Save. Otherwise, select Save to Disk and follow the steps in the next section, "Upload an AXTR file to BPM."


To enable the effective execution of your tests using automation tools, make sure all of your task recordings start on the main dashboard of your application.For end-to-end processes that are performed by more than one user, we recommend that you divide your task recordings into user-specific tasks. This simplifies the maintenance of test cases and allows you to execute test cases in the context of security roles, which is a best a practice.

Upload an AXTR file to BPM

If you have saved your recordings (AXTR files) to disk, follow these steps to upload them to BPM.

  1. In Lifecycle Services (LCS), in your project, on the Business process libraries page, select the library to upload the task recording to.

    (Video) Dynamics 365 for Finance and Operations: Acceptance Test Library Tech Talk

  2. Click Author and edit and in the lines, locate and select the process to upload the task recording to.

  3. In the right pane, click Upload.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (4)

  4. Click Browse to find and select the file to upload, and then click Upload.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (5)

Save an existing task recording to BPM

  1. To attach an existing task recording, sign in to the client.
  2. Go to Settings > Task recorder.
  3. Select Edit Task Recording and attach the file by either saving directly to LCS or downloading the AXTR and then uploading to BPM.

Guidelines for recording test cases

Follow these guidelines when authoring and recording your test cases, especially if you are planning to automate test execution.The process and tools described in this article apply to business process acceptance tests. They are not meant to replace component and unit testing that is typically owned by developers.

  • Author a limited number of test cases that, when combined, cover complete end-to-end processes.
  • Focus on business processes that have been customized.
  • An individual test case (recording) should cover one or two business tasks only, typically executed by one person. This simplifies task recording maintenance. Do not combine a complete end-to-end business process such as "Procure to Pay" or "Order to Cash" into one large task recording. For example, instead of having RFQ > Purchase Order > Product Receipt > Vendor Invoice > Vendor Payment as one test case, divide the process into three or four test cases. You will have the opportunity to combine these tests into an ordered test suite later.
  • A test case should have at least one validation. Try to validate critical fields that cover the impact of other fields. For example: Validation of totals on sales or purchase orders cover the unit price/quantity/discount/tax ...etc.
  • Avoid printing a report in a test case. If a test case needs to print a report, it should be selected on screen.
  • 80+% of test cases should be of transactions or source documents. Master data should be limited to up to 20% of test cases only.

Synchronize and configure your test plan in Azure DevOps

An acceptance test library is your starting point. It typically contains all test cases (task recordings) of a particular application organized by business process. During a particular test pass, you usually do not need to execute all test cases. What test cases you select depends on the phase of your implementation or the nature of the update you are planning to apply to your production environment. Azure DevOps enables you to organize your test cases in test plans and test suites. A test plan contains one or more test suites (A subset of your test library); test cases can belong to more than one test suite.

Once you have selected your acceptance testing BPM library, synchronize it with Azure DevOps and create your test plan and test suites.

Sync with Azure DevOps

Synchronize your BPM library with your Azure DevOps project. For more information, see Synchronize BPM libraries with Azure DevOps.

After configuration is complete, synchronize the BPM library with a Azure DevOps project.

  1. 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.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (6)

    You can also start Azure DevOps synchronization from the toolbar in a BPM library. Select the ellipsis button (…), and then select Azure DevOps sync.

    (Video) How to Automate Integration Testing in Microsoft Dynamics 365 Finance and Supply Chain Management

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (7)

  2. After Azure DevOps synchronization is complete, select the ellipsis button (…), and then select Sync test cases.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (8)

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

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (9)

In addition to the test steps, the task recording XML file is attached to the Azure DevOps test case. This file will be needed if you want to automate test execution.

Create a test suite in Azure DevOps

Next, you will need to create a test plan and test suite in Azure DevOps. This will allow you to execute an ordered suite of test cases and easily manage, investigate, and track the results.

  1. Sign in to Azure DevOps and select the project and test plan that you want to test in.

  2. On the toolbar, select Test > Test Plans.

  3. In the left pane, select +, and then select Static suite.

  4. Enter a name for the suite.

  5. Click Add existing and query the tag LCS:Test Cases.

  6. Click Run > Add test cases.

    (Video) Automate all your tests in Dynamics 365 Finance and Operations - Aurélien CLERE

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (10)

  7. Select the test case to view details and the attached XML file.

    Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (11)


This example shows how to create one comprehensive acceptance test suite with all test cases added. Instead, you should create various test suites under the same test plan and then use custom queries to add specific test cases to a test suite. A test case can belong to more than one test suite.

Execute your tests

Run manual test cases

After you have a test suite, you are ready to use it for regression testing after updates have been made to your application in a sandbox or test environment. You can run the test cases in your test suite manually or play the task recordings that are part of the test suite and use Azure DevOps to mark the test cases as passed or failed.

Create and automate user acceptance tests - Finance & Operations | Dynamics 365 (12)

Azure DevOps also provides a tool, Test Runner, to manage manual test case execution. For more information about using Test Runner, see Run manual tests.

We recommend that you take advantage of Azure DevOps as it provides a rich set of management features not only for testing, but result management and mitigation.

Run automated test cases

The platform for finance and operations provides developers with tools to author test cases based on task recordings and use Azure DevOps to manage the automated execution of these test cases.

Developers can use the build and test automation capabilities of build and test environments. For details, see the Continuous delivery home page.

Functional power users can automate the execution of their test cases using the Regression suite automation tool. For more information, download the tool and read the Regression suite automation tool.

(Video) Dynamics 365 - Test Strategy for Finance & Operations Implementations Tech Talk

Investigate test runs

Once an automated run is complete, on the Azure DevOps toolbar, select Test > Runs (or Test Plans > Runs) to investigate your test run. Select the desired test run to investigate test case failures and errors. You can also go to your test suite in Azure DevOps to see the latest results associated with your test cases.For more information on testing and test management in Azure DevOps, see the Azure DevOps documentation.


Can user acceptance testing be automated? ›

What Is User Acceptance Testing Automation? Automated UAT is when you and your quality assurance (QA) team use scripted tests that run automatically within an automated testing tool.

How do you create a user acceptance test plan? ›

Creating The UAT Test Plan
  1. Create Certain Signed Off Requirements. The general goal of UAT is to make sure that all of the client's requirements of the product are met. ...
  2. Reviewing The Test Scenario By The User. ...
  3. Make Sure That All Code is Delivered On Time. ...
  4. Use the Right Tools. ...
  5. Set the Criteria. ...
  6. Document Everything Properly.
24 Feb 2020

What are the 4 types of acceptance testing? ›

Types of acceptance testing include:
  • Alpha & Beta Testing.
  • Contract Acceptance Testing.
  • Regulation Acceptance Testing.
  • Operational Acceptance testing.

What is automated acceptance testing? ›

Automated acceptance tests deliver business value the users are expecting as they test user scenarios. Automated acceptance tests executed and passed on every build help improve the software delivery process. Testers, developers, and customers need to work closely to create suitable automated acceptance test suites.

What are the two types of UAT? ›

The following User Acceptance Testing Types exist: Alpha & Beta Testing. Contract Acceptance Testing. Regulation Acceptance Testing.

Which tools is used for UAT testing? ›

A few common UAT challenges that can be effectively addressed with a good test management tool include:
  • Poor end user engagement. ...
  • Test documentation challenges. ...
  • Test scheduling challenges. ...
  • Test Management challenges. ...
  • Atlassian Jira Software.
  • Zephar Application.
  • Rally Software.
  • Tricentis qTest Platform.
26 Mar 2021

How do you write a test script for UAT? ›

A few additional tips for writing effective UAT scripts include: Make test cases easy to do – Put yourself in the shoes of the tester when writing test scripts and make sure the scripts are concise and clear. Remove bias from your statements – Using biased language can affect the results of the test.

What are the 6 stages of acceptance testing? ›

The 6 Steps of Testing to get to “Final Acceptance”
  • Stage 1: Factory Acceptance Test.
  • Stage 2: Customer Acceptance Test.
  • Stage 3: Site Acceptance Test.
  • Stage 4: Coverage Verification Test.
  • Stage 5: Final System Acceptance Test.
  • Stage 6: Burn In Period.
25 Oct 2012

What is a UAT template? ›

User acceptance testing templates are documents that help QA teams plan and execute UAT testing. The end goals are: to find out if end users run into any issues when testing; and that the software works in a real world business context.

How do you do UAT user acceptance testing? ›

How to Conduct User Acceptance Testing: Process Stages, Deliverables, and End-User Testing Place in Quality Assurance
  1. Analyze product requirements and define key deliverables. ...
  2. Choose the time and form of end-user testing. ...
  3. Recruit users and form UAT team.
  4. Implement end-user testing tools and onboard testers.
19 Aug 2021

Is acceptance testing and UAT same? ›

Acceptance testing or User acceptance testing (UAT) is another classification of software testing performed by the customer before accepting the final product. Generally, acceptance testing is used to evaluate whether the application works as per the specified business requirements or real-time scenarios.

What is user acceptance testing with example? ›

User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.

What are the three levels of acceptance testing? ›

The software has passed through three testing levels (Unit Testing, Integration Testing, System Testing). Some minor errors can still be identified when the end-user uses the system in the actual scenario.

What is automated testing and how does it work? ›

Automated testing is a process that validates if software is functioning appropriately and meeting requirements before it is released into production. This software testing method uses scripted sequences that are executed by testing tools.

Who should write acceptance tests? ›

Requirements authors. Business stakeholders including independent subject matter experts. Technical and other specialist experts. The organisation's specialist test team, assuming that it has one.

What is the difference between testing and UAT? ›

In general, testing is done by both testers and developers. Each of them follows its own pattern to test an application. System Integration Testing or SIT is done by testers whereas User Acceptance Testing, commonly known as UAT is done lastly by the end-users.

What is user testing vs UAT? ›

What Do the Tests Do?
Usability testingDoes the product produce a good user experience? Does it allow users to effectively, efficiently and comfortably achieve certain objectives?
User acceptance testingIs the product fit for purpose? Does it enable users to achieve certain objectives?
29 Aug 2022

Is UAT part of Agile? ›

User-acceptance test (UAT) is a part of acceptance testing in agile development. But acceptance test might also include non-UAT tests such as traditional functional or system test created by the team. Ideally, all the acceptance testing—including UAT—is done within the iteration.

What is a UAT workflow? ›

User Acceptance Testing (UAT), or application testing, is the final stage of any software development or change request lifecycle before go-live. It is the final stage of any development process to determine that the software does what it was designed to do in real-world situations.

Who is responsible for UAT scripts? ›

Usually, UAT is undertaken by a Subject Matter Expert (SME) and /or a business user, who might be the owner or the customer of a system under test. Similar to the System testing phase, the UAT phase also encompasses religious phases before it is brought to closure.

Who does UAT testing in agile? ›

UAT, or user acceptance testing, is the final stage in the software testing process. It is typically performed by the end-users or client to determine whether an application or feature fulfills its purpose. UAT must be completed before the software can be released to the market.

What are the 4 phases of the testing framework? ›

They are executed sequentially.
  • setup. During setup, the system under test (usually a class, object, or method) is set up. ...
  • exercise. During exercise, the system under test is executed. ...
  • verify. During verification, the result of the exercise is verified against the developer's expectations. ...
  • all together.
10 Mar 2022

How do you manage UAT testing? ›

How to Manage User Acceptance Testing
  1. Determine Correct User Roles. One of the most important items to define first is who from the team will be involved in the UAT process. ...
  2. Choose the Type of Testing. ...
  3. Determine Time frames. ...
  4. Determine Documentation Standard. ...
  5. Determine the Change Control Process.
11 Nov 2013

What are the major objectives of user acceptance testing? ›

The goal of User Acceptance Testing is to assess if the system can support day-to-day business and user scenarios and ensure the system is sufficient and correct for business usage.

What comes first UAT or QA? ›

After QA, UAT is usually the final testing process prior to code deployment. The software development organization delivers the product to its client, which performs its own assessment of the work. Client testers perform a UAT process to determine if the system, as tested, satisfies business needs.

What is the difference between user acceptance testing and business acceptance testing? ›

There are various forms of acceptance testing: User Acceptance Testing (UAT): This involves verifying if the user's specific requirements have been met. Business Acceptance Testing (BAT): Here you are assessing whether the product meets the business goals set out in the design.

What are the 5 basic principles of testing? ›

The seven principles of testing
  • Testing shows the presence of defects, not their absence. ...
  • Exhaustive testing is impossible. ...
  • Early testing saves time and money. ...
  • Defects cluster together. ...
  • Beware of the pesticide paradox. ...
  • Testing is context dependent. ...
  • Absence-of-errors is a fallacy.

What is the another name of acceptance testing? ›

It is also known as user acceptance testing (UAT), operational acceptance testing (OAT), and end-user testing. It is one of the final stages of the software's testing cycle and often occurs before a client or customer accepts the new application. Acceptance tests are black-box system tests.

What are the challenges for acceptance testing? ›

The main UAT challenges are:
  • Determine Correct User Roles. ...
  • Choose the Type of Testing. ...
  • Environment Setup and Deployment Process. ...
  • Determine Time Frames. ...
  • Determine Documentation Standard. ...
  • Determine the Change Control Process. ...
  • Test Planning. ...
  • Handling New Business Requirements as Defects.
18 Feb 2015

What are the 4 types of automation? ›

There are four types of automation systems: fixed automation, programmable automation, flexible automation and integrated automation. Let's take a look at each type and their differences and advantages. Then you can try to determine which type of automation system is best for you.

What is example of automation testing? ›

Example of Test Automation

Selenium is an open-source framework for cross-browser and cross-platform testing of web applications. It is a suite that allows automated tests of websites and web applications in different browsers on different platforms using any programming language of your choice.

What are the three basic steps of automation? ›

The first phase is enhancement, the second phase is assistance and the final phase is replacement.
  • Enhancement. In the first phase, automation extends a human's abilities, but it still requires a human to do its work.
  • Assistance. ...
  • Replacement.
19 Jun 2018

Is UAT testing done manually? ›

UAT is usually done manually, with users creating real-world situations and testing how the software reacts and performs. Test-case scenarios can also be automated, simulating a user experience. As its name suggests, UAT is used to determine if end-users accept software before it's made public.

Can selenium be used for acceptance testing? ›

Selenium automates acceptance testing (or functional testing) for webapps by simulating a user's interaction with the webapp through remotely controlled Web browser.

How is user acceptance testing done? ›

User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.

What is a limitation of acceptance testing? ›

The disadvantages include: You might not test all functions or features. Test progress is difficult to measure. users might conform to the way the system works and not see or report the defects.

What is UAT testing example? ›

For example, a UAT plan may describe things found in other test plans, such as schedules, roles, risks, environments and tools. But a UAT test plan is often oriented to business or user test objectives as opposed to system test objectives. This is a nuance often missed in planning UAT efforts.

What is the difference between acceptance testing and user acceptance testing? ›

Generally, acceptance testing is used to evaluate whether the application works as per the specified business requirements or real-time scenarios. UAT testing is executed on the customer's unique environment, which is acknowledged as the UAT environment.

How cucumber is used in acceptance testing? ›

Cucumber does this by starting a browser in the background, and doing what a real user would do by clicking on links, filling out forms, etc. You should not use Cucumber to unit test your JavaScript-drivencript code, but it's perfect for testing user interaction.

Which Selenium framework is best for automation testing? ›

Selenium WebDriver: Selenium WebDriver is most used and helpful in running the Selenium tests across the browser. Selenium RC: Selenium RC helps write test cases in different programming languages to automate UI tests for web applications against any HTTP website.

Why is user acceptance testing necessary? ›

UAT is important because it helps demonstrate that required business functions are operating in a manner suited to real-world circumstances and usage. If the expected outcome is not achieved during testing, the item will be documented and sent back to the developers for repair.

Which one is the main focus of acceptance testing? ›

The major aim of this test is to evaluate the compliance of the system with the business requirements and assess whether it is acceptable for delivery or not.

What challenges you have faced while doing UAT testing? ›

Here are some of these challenges that you might face during UAT:
  • Mimicking the right testing environment. ...
  • Determining time frames. ...
  • Reviewing your test plans. ...
  • Ambiguous requirements. ...
  • Asking functional test team to perform user acceptance testing. ...
  • Single-purpose UAT environment. ...
  • Priority-based UAT environment.


1. Test Strategy for Dynamics 365 Finance & Operations
(Microsoft Dynamics 365)
2. Automated Testing Strategies for Dynamics 365 for Finance and Operations
(Microsoft Dynamics 365)
3. User Acceptance Testing Can Make Or Break Your Dynamics 365 Project
(Prophet Business Group)
4. English HowTo #1 - Dynamics 365 F&O with RSAT (Automated Testing)
(Aurélien Clere)
5. How To Test MS Dynamics 365 for Finance & Operations Through The UI | Automation Webinar Series
6. Dynamics 365 Regression Suite Automation Tool Tech Talk
(Michael Cobbin - Dynamics 365)
Top Articles
Latest Posts
Article information

Author: Stevie Stamm

Last Updated: 02/06/2023

Views: 6342

Rating: 5 / 5 (80 voted)

Reviews: 95% of readers found this page helpful

Author information

Name: Stevie Stamm

Birthday: 1996-06-22

Address: Apt. 419 4200 Sipes Estate, East Delmerview, WY 05617

Phone: +342332224300

Job: Future Advertising Analyst

Hobby: Leather crafting, Puzzles, Leather crafting, scrapbook, Urban exploration, Cabaret, Skateboarding

Introduction: My name is Stevie Stamm, I am a colorful, sparkling, splendid, vast, open, hilarious, tender person who loves writing and wants to share my knowledge and understanding with you.