Several criteria must be taken into account in order to estimate the relevance of using test tools for its EDI platform. Among these:
- What is the type of platform? EDI Web, ASP or in situ?
- What is the frequency of changes? How often are changes pushed to production?
- How many tests are there? This number will be strongly correlated with the previous point, as well as the number of different flows, mappings, partners and the complexity of the Information System.
For example, for a Web EDI platform, with 2 changes per year and less than 50 mappings, it is not necessary to use testing tools. The management of tests can be done using a spreadsheet for example, and the generation of a report can be done with a text editor or in the spreadsheet directly. Finally, the tests can be executed manually, sending the EDI messages via the web portal.
In contrast, an in-house EDI platform, modified several times a week, with a few hundred mappings, will certainly require a real test infrastructure, with appropriate tools to manage and run the tests, as well as generate reports for the go-live. Indeed, in such a situation, it is no longer possible to run the tests manually within a reasonable time. Moreover, it becomes necessary to have a history of modifications made in the platform that can be related to the different tests performed. Finally, it becomes necessary to use several test environments (development, integration, pre-production etc.).
A solution like Spindev is suitable in this case because it meets the different needs listed above. It is also possible to assemble different open-source or proprietary bricks, however, this requires a significant investment in development on technologies not necessarily controlled. To help you in your choice, checkout our article about the choice of test tools for your EDI platform.