Chaining Test Cases in Dynamics 365 for Finance and Operations

In a previous blog post, I wrote about how to automate regression testing using the Regression Suite Automation Tool (RSAT) with Dynamics 365 for Finance and Operations (D365F&O).

At the time, I promised to come back to how you link test cases using RSAT. Therefore, in this blog post I will explore this topic a bit further. In fact, linking test cases using RSAT is incredibly simple.

Capturing Values During Record

To link test cases, you need to capture one or more values to pass between the test cases.

In this example I have two test cases:

1. Create sales order.
2. Generate delivery note.

When executing my test plan, I would like to generate a delivery note (test case #2) for the sales order created in test case #1. To do this, I need to pass the sales order number from test case #1 to test case #2.

For this to happen, I need to capture the sales order number during task recording.

In the above screenshot, I am recording the process for creating a new sales order. Once the sales order number has been generated, I right-click in the field and select Task recorder / Copy.

The function does not copy the value itself, but the field meta-data.

Passing Meta-Data Downstream

The spreadsheet containing the task recording meta-data now has a section in the “General” tab called “Saved variables”. In cell A-15 in the spreadsheet below, you can see the reference to the sales order number we have just captured.

The reference value is: {{SalesTable_SalesTable_SalesId_3975_Copy}}

Now, if I open the task recording spreadsheet for the second test case (“Generate delivery note”), I can use this reference value to link the two test cases together.

As shown in the above screenshot, I have navigated to the “SalesTableListPage” tab in the spreadsheet for the second test case. In this tab there is a field reference called “Sales order”. This is because, in the second test case, I filter the sales order list page on sales order number to find the correct sales order. Instead of using a fixed value, I paste the value reference ({{SalesTable_SalesTable_SalesId_3975_Copy}}) from the first test case into Value cell. This way I pass the sales order number between the two test cases (by reference).

It really is that simple!

So in my scenario, the automated test will always create a new sales order (test case #1) and in the second test case, it will look up this new sales order and generate a delivery note for it.

Obviously, you need to get the sequence of the test cases right for this to work.

Since the reference value uses the test case number, it is possible to link across any number of test cases and also reuse the value several times. If for instance, I had a third test case that generated an invoice, I could also pass the sales order number to this test case using the same value reference.

Additional Reading

There is a short article on how to chain test cases on Docs.