Test Script for Uat Testing

1 UAT Functionality Testing

System test cases provide a grouping of similar discrete tests and their expected results. They are used to test the many different functional requirements and business rules identified during the design phase for the Screen or Process being tested. The test case should not be concerned with testing every specific field level validation and basic screen element tests; for example, testing if the title of the window is correct. The developer's unit test scripts should have caught all of these types of discrepancies and errors. If a tester does find something that slipped through unit testing, then they should mark the test case as FAIL and place the reason why in the comment field. Unique field level validation that has a significant impact on functionality can be written up as a test case to capture the importance of the functionality. Specific functionality that is required upon an event like selecting a button or a value in a drop down list should be recorded as a single test case. The fields of the test scenario template are described below:

Test Group: A logical test group code to quickly identify the test cases.

Author: The initials or the full name of the person who wrote the test script.

Prerequisite: Any prerequisite setup or application navigation that should have taken place before the test scenario can be executed correctly.

ID#: The test id of the test case.

Test Description: The detailed description of the test.

Expected Result Detailed description of what the expected result should be.

Pass/Fail: PASS if the test passed or FAIL if the test failed.

Tester: The initials or the full name of the person who executed the test script.

Comments: Any comments from the tester regarding questionable results or usability issues

This Users Acceptance test script is designed to test Journal entries for Transactions created/captured in Web Express on a daily basis and the creation of invoices for the amount payable to billers on a daily basis. The Activity transactions will be imported into Oracle from Web Express via a customized import process and the relevant processes run to generate the journal entries which are auto posted to the General ledger.

The following functional tests will be performed for Activity data generated in Web Express for the period:

1.1 Verification of Opening General Ledger Balances - The General Ledger balances will be generated first to ensure the user captures the opening balances