Regardless of company or industry, there is a continuous need for innovation and the use of different types of software. Thus, there is also the requirement for efficient and well-functioning application testing.

This has been seen as a given in large parts general software development and new innovations have long been built with the help of automated tests and continuous deployments. Why has automation not come further for critical ERP systems?

One reason is that ERP projects have used and are still using classic waterfall projects where speed has not been prioritized. A false (to some extent) security has been built up with few major releases instead of a more agile way of working, that put higher demands on automated program testing and a faster deployment rate. Another historical factor is that the hurdle to get started has been too high and the projects have built a technical debt that feels too heavy and costly to overcome. The suppliers’ strategies in the area have simply also been too weak. Thankfully, large steps have been taken in the right direction in recent years.

Take these steps to get started:

1. Secure support: Make sure the management thinks this is a brilliant idea and long-term necessity.
2. Get help: Get help from an expert and make sure you get started! Start by setting a reasonable initial scope, define a clear set of rules, appoint and educate those responsible, and choose the right testing tool.
3. Get started: Start with simple processes and build from there. Be sure to inspire and educate along the way so more key people realize the importance and benefits of automating.
4. Improve continuously: Everything should not be automated – you will continue to have prototype-, user- and certain function-testing that there is no point in automating. Get started first and improve gradually. Learning by doing.

Feel free to contact us if you want to talk about automated testing in general or Microsoft Dynamics 365 testing specifically. At Engage, we have a methodology that we have used to help several customers get started, carefully selected tools, and set the scope for automated testing of Microsoft’s monthly updates or our own functional releases. The whole idea is based on getting started quickly with implementation to gradually build the customer’s ability to drive testing.