Скачать или смотреть Poorly written test scripts is the #12 reason for digital transformation failure in 2023.

Just like your medicines have to go through multiple rounds of testing before they are ready for safer consumption.

Your ERP systems need to go through the same cycle as well.

The more you test, the better you get at testing.

But can your testing skills lead to digital transformation failure?

Let’s find out.

Recall the reasons we covered so far for digital transformation failure:
💠Misalignement in scope
💠Unrealistic expectations
💠Inability to re-engineer processes
💠Over-customization of the software
💠Usage of too many poorly written bolt-ons
💠Organizational change management
💠 Lack of maturity of enterprise architecture
💠Poor governance of master data
💠System selection gone wrong
💠Mimicking past results for future success
💠Ability to work with technology vendors

Software testing is a skill.

The people who don’t have a software background struggle to create comprehensive test cases.

Testing ERP systems is even different.

As you need to know the ERP functionality in depth.

To understand what needs to be tested.

If you end up testing core ERP functionality, you might lose millions of dollars without accomplishing anything.

This is where the testing gap analysis is handy.

So where do rookie testers miss the bus with testing?

Here are some examples of the test cases they might write:
💠Create and test 5 sales orders. With no clear goal in how these 5 sales orders might vary!
💠 Test how the ERP is rendering on mobile. Sure, this could be a test case if you are designing ERP from scratch. But for most products, this is probably not a meaningful test case.
💠 Test multiple variations of user name and password. This could be a great test case for a web app. But not for ERP.

See the trend?

Most are not meaningful.

Why?


Because they don’t attack the functionality that is likely to break with an ERP.

Here are some quality test cases:
💠Create a sales order and make sure the pricing is reflected correctly based on the customer and item selected.
💠Post an invoice and make sure it’s posted in the right GL accounts.
💠Login as the production manager and make sure he/she is not able to post journal entries.

These test cases are specific and attack the core functionality that is likely to break due to the ERP configuration.

Also, the ERP test cases are one of the hardest to document.

Why?

Due to the number of variables and outcomes involved with the testing.


So it’s even harder to ensure test coverage.


The implications of poor test coverage?
Disruptions after going live
Poor adoption
Surprises
Missing key functionality


Has poor testing coverage fired back for you? How bad?

—-----------------------------------------------------
💠 Have you checked our digital transformation report for 2023 yet? It covers what to expect with ERP and eCommerce market in 2023 in deep detail. If not, download at t.ly/-DVk
💠Ring the 🔔 for notifications!

#ERP #Testing #QualityAssurance