Testing automation

There are several testing capabilities for Dynamics AX Dynamics 365 for Finance and Operations (D365FO). It is import to understand the value of automate testing and where to use which tool/technique.

You can’t avoid, at some point you will have to test your solution.

Ideally, after every change in your system you will have to test it again. If you have to go over the same process multiple times, why not automate to save some time and money ?

The testing pyramid

Thinking about Return Of Investment (ROI), the ideal number of tests you have in your environment is:

Unit tests are very small and fast to run - that’s why you want to have lots of these. Business cycle tests are slow to execute and hard to maintain.

---

Unit test: It validates if a unit of your X++ code behaves as expected.

Component test: It validates if your component works as expected and met the functional requirements (of the component).

Integration test: Validates the interactions between several components. Validates the functional requirements.

Business cycle test: Validates end to end scenarios. Simulates a real user and validates the functional requirements.

---

The RSAT tool

Microsoft released a Regression Suite Automation Tool (RSAT). It is a great tool to automate some of your tests, but be aware, this should be used for Business cycle testing.

RSAT tool will simulate the user and perform all actions through the UI. It means it is slow to run.

If you have X++ customization in your D365 project you definitely should be doing unit, component and integration testing using SysTest, not only RSAT.