Introduction
To test and evaluate the customer solution prior to go-live, you need to have an environment of finance and operations apps, with all the configurations and possible customizations through extensions.
It is always beneficial to have a methodology to ensure that creation and testing is organized and planned properly for short, efficient, and role-focused test case scenarios.
To validate the solution that might have been customized by extensions, or when you are identifying possible issues with functionality of finance and operations apps that were caused by wrong configuration, you need to create test cases. Test cases can help you, as a functional consultant, and users to approve the user acceptance documents.
You can use the task recorder and business process modeler (BPM) to create user acceptance test libraries. The task recorder is a powerful tool to record test cases, and you can organize them by business processes by using BPM.
You can use BPM to distribute test libraries to your customers through Lifecycle Services and Lifecycle Services solutions. You can also use BPM to write and distribute test libraries across different projects and teams.
Because BPM can be synchronized with Azure DevOps (formerly known as Visual Studio Team Services), test cases are automatically created (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 running of tests, and investigate results.