We all know it: after every modification in D365FO, countless processes have to be checked and run through. Questions arise such as: Can the individual…
We all know it: after every modification in D365FO, countless processes have to be checked and run through. Questions arise such as: Can the individual processes be carried out by the users as usual? Is the expected value displayed / calculated? Nobody likes to release a version without knowing whether the system still works afterwards. This topic has been relevant for years and the fight against the windmills is being waged in various places: Quality controls at the manufacturer (Microsoft) Testing by the partner before handing over a modification to the customer The customer tests the processes with the key users and signs them off Due to the complexity of today's systems, predicting what side effects come with an update is also becoming ever more difficult and costly. Wouldn't it be nice if a «good fairy» could check the most important processes every evening? Before such a check, however, the first step is to define what the most important processes actually are: every company has different core processes that must under no circumstances be affected by a modification. In a first step, therefore, it should be defined precisely what is to be tested and how these tests can also be run reproducibly. Only once this has been clarified can a technical implementation be started. In this post I look at the options for automated testing in D365FO and present the possibilities using the following 2 variants, then compare them with one another. The advantages and disadvantages of the 2 variants are presented from my own personal point of view. RSAT from Microsoft Executive Automats RSAT (Regression Suite Automation Tool) The official test tool from Microsoft. The idea is simple and straightforward: A user records a process with the Task recorder, which can then be played back automatically. The task created in this way is then saved in LCS. DevOps (D365's code management) synchronises with LCS, and here several tasks can be combined into one process. A program that runs the