Test Scripts are an important tool to help you ensure your ERP system, or part of it, is ready to go live. Testing random, incomplete transactions with random data will give you results but probably not the results you need to help you feel ready to go live with your implementation.Test Scripts are intended to provide instructions for testing specific functional areas of the software in a controlled manner. They include the typical steps to complete a task, as well as some alternative steps that may be required to accommodate exceptions. The instructions must be based on known processes and known exceptions to ensure measurable results.

Configuration of the system, for the functional area being tested, must be completed prior to testing to prevent any unnecessary interruptions. The User Acceptance Testing (UAT) is intended to address the data entry and reporting processes, and not to deal with errors due to missing configurations, setup, user permissions or errors in custom programming.

It’s recommended to start off the Test Script document with an overview of what the user will be doing. Identifying the expected result for each process will help the users be successful with their testing. Including a description of the state of the system before the testing process can help the users feel assured that the system is ready for them to proceed. Also, try to help them understand why the steps will be performed in the order specified so they are encouraged to follow them.

Test Scripts should only include enough detail for the level of user that will be performing the test. Too much detail can be confusing and can waste time. Not enough detail can leave the user unsure about what they need to do or how they are to do it. Remember, you want them to test the system, not test their knowledge of the system. It’s important that they be successful with their testing.Including examples of the data to use can help control the testing and ensure success. This can also help the users relate the Test Script to their day-to-day tasks and to better understand the testing process. Provide enough data examples so the users can repeat the testing process a reasonable number of times to confirm the test results. Last but not least, be sure to test your Test Scripts before giving them to the users. Make sure the data they need is either include in the script or already in the system and that the steps you’ve documented are correct. You don’t want the users to get frustrated because the system isn’t ready for them.