DO – base your test scripts on a ‘requirements tracking matrix’ and your processes. This way you ensure you are using real world cases, as well as covering all requirements that you have defined. There should be a list of test scripts to be tested for each system change.
DO – keep a master test log with all scripts, associated owners and status. The testing coordinator will have a quick reference for testing progress.
DO – develop and maintain test scripts with the goal of re-use throughout the life cycle of the system.
DO – have a subject matter expert validate test results and sign off, even if testing is automated or delegated. Testing can be time-consuming but will ensure a smooth transition to support.

DON’T – think of testing as some mechanical, rote activity that you just have to plow through. Software testing is a discipline of its own, and a good tester asks good questions, listens to the customers, and is always concerned with quality.
DON’T – be tempted to skip testing. Even if it is a simple change or you have made similar changes many times – passing a change with an obvious error to the client causes annoyance and hurts confidence.
DON’T – be surprised that a change to another entity’s settings in a shared system somehow affects your processes. If you don’t know exactly the extent of the change you are doing – ask for advice, share with the team and test!
DON’T – wait till the last minute, but start planning your testing activities in the design phase. Think about how you will present testing results to different stakeholders, and make sure you seek feedback about your process. Correcting issues will take time, so ensure you get the testing process right from the start, otherwise you might be looking at delays.

Looking for a partner to help with your SAP HCM testing?  Contact us