What will low code or no code mean for ERP software testing?

By Tyler Price

There was a time when people used to say, “if you want a job for life, become a plumber”. A modern equivalent might be “become a coder”. One thing the tech marketplace is not short of is demand for new software. However, in recent years we have seen a move towards the concept of low code development, where there is less emphasis on the requirement for technical coding skills. Taking this concept one step further is the principal of no code, where non-technical users are able to develop applications using intuitive drag and drop functionality and don’t need to write any code at all.

I’m not a coder, so I’ll let SAP provide a formal definition:

Low-code: Is a method of designing and developing applications using intuitive graphical tools and embedded functionalities that reduce traditional – or pro-code – writing requirements. It offers an augmented and simplified experience to help users start creating quickly.

No-code: Is a method that benefits from a similar user experience as low-code, but goes the extra mile by allowing non-technical business users to develop applications without having to write even a single line of code.

If low code or no code is a viable option, it has some obvious benefits. Ease of use is a given, as is cost-effectiveness. Coding is a highly sought-after skill and commands a premium. If functionality can be introduced without the need for an expensive resource, all the better. The nature of low code or no code also lends itself to increased process automation and faster development lifecycles, meaning new functionality can be brought to market quicker.

It should come as no surprise to hear that a recent Capgemini reports indicates almost half of executives polled are looking to take advantage of low/no code in the coming year.

The concept of low code or no code does have some limitations that become more evident the more complex a development project becomes. Generally speaking, the more complex the solution, the more likely you are to need specialist coding skills. ERP is a prime example. Developing software of the scope of JD Edwards EnterpriseOne or Oracle cloud applications is going to require coding expertise, but there may be some elements of the software lifecycle, like testing, that could benefit from low/no code.

Ease of use sits at the core of the ERP functional testing software we develop. In fact, our SwifTest solution was specifically built with non-technical users in mind. You don’t need to have coding skills to build, edit, execute and audit your own test scripts. This makes testing quicker and easier, helping businesses to make significant savings on project timelines, and costs. Or, as we like to put it, to run smaller, faster, smarter projects.


Useful links:

SwifTest Webpage

10 ways test automation adds value to your ERP functional testing

DWS Logigear Logo
DWS Logigear logo3 (1)