Tip 2: Understand and continuously measure your testing

It’s critical to understand the scope of testing.  Whether you are doing test automation, test outsourcing or manual testing, you need to know the programs and versions that your users are currently using.  This is going to allow for accurate test scenarios.  Knowing your programs (both interactive and batch) will allow you to also choose candidates for automation (if that is what you are going to do).

A high level idea of your processes (whether documented or reverse engineered by clever e1 pages) will enable you to group your test cases and test resources.  Quite often a logical grouping of your testing can ensure that end to end processes are tested and that the test data is going through a full cycle too.

Get a good list of programs and how often they are used.  Get a good list of users from production and what programs they are running.  Use these two project assets to then choose a test team and also ensure test case saturation in your test environments.

Figure 2: Using the Fusion5 ERP Analytics suite, you can quickly see programs and how much their usage is, using a date range and environment.

At Fusion5 we advocate the use of ERP Analytics to give you “easy to use” reporting on all user activity in JD Edwards.  This software subscription can plug into your current production environment and your upgraded environment and provide constant feedback about test volumes and test case saturation – for both batch and interactive.