Protecting and Maximizing ERP Investment through Testing
Transitioning to enterprise resource planning (ERP) systems such as SAP S/4HANA and Infor CloudSuite requires enhanced testing processes, as the rise in update frequency—from annual to monthly releases—makes traditional testing methods more challenging. An article from ERP Today discusses strategies for safeguarding and maximizing investments in Enterprise Resource Planning (ERP), such as SAP S/4HANA or Infor CloudSuite. As frequent updates and complex application landscapes become the norm, organizations face increased challenges in ensuring software quality and stability. Colin Armitage, CEO of Original Software, emphasizes that their low-code/no-code testing platform simplifies automation by avoiding the pitfalls of traditional code-based solutions, making testing more accessible and adaptable. The platform efficiently manages timing issues and supports a wide range of applications, including legacy systems and multiple ERP environments, facilitating seamless end-to-end process testing across diverse tools. With the rise of rapid, monthly ERP updates, traditional testing approaches are no longer viable. Organizations must prioritize critical process automation—creating “survival packs” of tests for core functions—and consider targeted support services to accelerate testing efforts. Armitage also notes the strategic role of AI in improving test readability and efficiency, exemplified by cost savings at Costco. Finally, the article underscores the importance of building a compelling business case for testing investments, especially as the frequency of software updates increases. Partnering with experienced professionals like your current managed services provider or providers like Original Software helps companies adapt to the fast-changing landscape, mitigate risks, and ensure their ERP investments deliver ongoing value.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
