Skip to main content

AX and Scrum: Automated testing

Scrum highly encourages you to do automated testing. A common thing I hear is “any (some) automated testing is better than none”. So, my advice is start somewhere.

I am not going to go through all the detail of automated testing that we do but what I will cover is the Unit test framework. The unit test framework is in the MorphX IDE that allows you test your code. A click of a button you could run a whole bunch of automated tests.

Below is a screen shot of an area we test heavily, our forecasting engine. The forecasting engine similar to master planning in standard AX. It recommends what work order should be done and when. eg. Every 100KM a service is required for your car. Or Every 6Month you do an oil change. Or on the 1st of of every month you do an inspection. All sorts of combinations.


Below is a simple test for testing calendar days. We document our test cases in a spreadsheet first. Writing what the input is and what the out come is. Then a developer writes a test suite or adds to an existing test suite.


Writing unit tests is expensive but it is more expensive to not do it. Imagine you make one little change that breaks a number of areas of the system. You will never pick it up manually until a customer runs into it in production. Now that is costly in a number of ways. Now imagine you could automated a number of scenarios and run it in under a minute.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi