Skip to main content

Automated testing #MSDyn365FO Odata with Postman

In the last post I did a quick run through on using Postman for testing Odata services.

This post I will give some tips on how you can write automated tests using Postman.


Tip 1 – Parameterise as much as you can

Parameterise using the environment settings. It will make your collection portable to other projects.

Below is an example where we have the environments settings parameterised.

image

You can see how I used it here. Now I can utilise the same thing across requests.

image

Tip 2 – Write test scripts

Test scripts are very easy to work with. This is for demonstration purpose only. I will explain how you can retrieve the values in the returned json.

Take the example here, where we use the “get customer” odata service. It returns a nested array with the values.

image

You can write a simple test script to retrieve values. In the below highlighted box you can see that I am logging it to the console. I am not really testing much here.

image

The console will return the below. 

SNAGHTML1377b4

One bonus tip here. Just click on the snippet codes to get sample code from Postman. Really helpful.

image

Tip 3 – Automated testing

Usually you will have dependent requests. The first request in our example retrieved the OAuth token and saved it in the environment settings. For the second request to work, it must get a fresh token to authenticate.

To run the collection, click on Runner at the top left of the main window.

image

Once the runner window opens up. Select you collection or folder. Then click on Run button at the bottom.

image

Once complete, you get your result.

image

If you are new to all this. I would recommend taking a look at postman blog on automated testing.

http://blog.getpostman.com/2014/03/07/writing-automated-tests-for-apis-using-postman/

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.in(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