RSAT is an automated testing tool that allows organizations to automate testing for their business processes in D365 Finance & Operations.
First, you need to define your test plan, test suite and test cases in Azure DevOps
- Test plan = RSAT
- Test suite = Indirect procurement
- Test cases = Purchase order creation
There are Microsoft links that explain very well the steps to set up RSAT. Personally, I would focus on some some guidelines to follow :
- An individual test case (recording) should cover one or two business tasks. Do not combine a complete end-to-end business process in one recording
- A test case should have at least one validation. Try to validate critical fields that impact other fields
- Avoid printing a report in a test case
- About 80% of test cases should be of transactions type and master data should be limited up to 20% of test cases
- Avoid refreshing a page while recording your test
- Always set the Edit mode of the environment to Read or Edit
- Download the Extension to have the feature for Google Chrome to take screenshots
- RSAT relies on Azure DevOps to store and manage test recording files. Azure DevOps can be used as a test repository
- Save task recorder files against test cases as a developer recording (we don’t use BPM in LCS in that instance)
- Name the recording file Test Case 1-.xml, where Test Case 1 is the title of the test case in Azure DevOps
Within RSAT, it is critical to consider how well-planned task recordings may support your automated testing.
By adding task recorder functions and validation steps, you can devise robust process scenarios that RSAT will understand and execute.
While recording, right-click the field you want noted in RSAT, select “Task recorder” then click “Copy”. This action will create a variable once RSAT generates the parameter files. Task recorder functions as Copy & Paste are not viewable in the recording but are used by RSAT. They make note of fields and convert those fields into variables which can be used to link your test cases together.
Validation steps are also crucial when the expected results should be verified as part of the test case.