In Supply Chain world, EDI is the mode of communication between two computer systems, in B2B space. It is interesting to think about how to do Software Testing for this. With the advent of API, there has been discussions going on whether to use EDI or API. It seems for most practical purposes, API has been accepted by people who implement and serve the supply chain clients, but whether the clients are happy with it or not is still an open question. Let’s talk about EDI and API in this blog.
Either way, the communication channel is key in the digital interactions between systems, so I am going to delve into this subject in detail in a few blogs from now on. The communications is nothing but about protocols, and protocol testing is an involved area by itself with considerations about whether state or stateless, delays and handling, validating and verifying protocol parameters, etc.
I would first share with you, a perspective of EDI vs API. From there on, we will look into detail the standards details, and the Software Testing aspects of the protocols. Here’s some interesting stuff to mull on. Feel free to contact me for Testing strategies.
Pingback: Complexities in testing EDIs – Test Musings, by Venkat Ramakrishnan