How Do We Develop Acceptance Test Scripts? It is important to always maintain the relationship between any Test Case and the requirement or acceptance criterion it is verifying. There are two steps to follow when developing Test Cases: ►Step 1is to describe what is needed for each Test, what is to be done, and the expected outcome. A Test Case template is included as part of this Kit. ►Step 2is to document the required Test Data and conditions that enable the Test to be undertaken. To help you in developing your Tests, a Test Case and Script checklist has been included as part of this Kit. For each Test, determine: ►The features to be tested; ►The source database(s) that will be required; ►The source of data required specifically for the Test; ►Any other resource requirements; ►The task that will be performed in the Test Case; and ►The expected outcome. Once Test Cases are prepared, collate related Test Cases into Test Scripts. Each Test Script usually equates with a business process. The Script brings all related Tests together into a logical sequence. For example, in a financial system there may be a series of tests to record different types of on-line financial transactions and there may be other tests to create and post a batch of transactions to the system and to print a batch report. It makes sense to relate the on-line transaction entry to the subsequent batch posting and printing. If new business processes are involved, describe in the Test Script the overall approach required to test them,
The Acceptance Testing Kit – Part 2 22End-users familiar with the application area and system are best for creating test data. To minimise data contention between tests, discrete test data may be assigned to one or several (related) Test Scripts.including the normal and alternative paths, and key exceptions. For each Test Script, identify resource requirements, including any resources outside the organisation. A Test Script template is available as part of this Kit. What Test Data Should We Use? Preparing Test Data can be a time consuming process. To minimise effort, first validate Test Data and then preserve it for subsequent re-use should it become corrupt through failed tests. It may be possible to create data via direct data entry or by electronic transfer (such as exporting from a spreadsheet and direct loading into the test database). Test Data may also be taken from standard input forms used within the Business Unit. In some instances where the data is not of great significance, the Tester will be required to “make some up”. A useful source of data (especially where large volumes are required) is data migrated from an existing system. However, the data migration and load processes require thorough testing themselves and often migrated data may be incomplete and of questionable quality.