TE.040 System Test Script - Fixed Assets

Doc Ref: <Document Reference Number>

TE.040 System Test Script

XXX 0, 0000

AIM

TE.040 System Test Script

Fixed Assets

Author:<Author>

Creation Date:May 16, 1999

Last Updated:XXX 0, 0000

Document Ref:<Document Reference Number>

Version:DRAFT 1A

Note:Title, Subject, Last Updated Date, Reference Number, andVersion are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->Options…View and checking the Bookmarks option in the Show region.

Approvals:

Note:To add additional approval lines, press [Tab] from the last cell in the table above.

<insert company logo here> Copy Number_____

Note:You can delete any elements of this cover page that you do not need for your document. For example, Copy Number is only required if this is a controlled document and you need to track each copy that you distribute.

Document Control

Change Record

Date / Author / Version / Change Reference
16-May-99 / <Author> / Draft 1a / No Previous Document

Reviewers

Name / Position

Distribution

Copy No. / Name / Location
1 / Library Master / Project Library
2 / Project Manager
3
4

Note:The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Contents

Document Control

Overview

System Test Sequences

System Test Specifications – Add Assets Manually (Detail)

System Test Specifications – Add Assets Manually (Quick Additions)

System Test Specifications – Add CIP Assets

System Test Specifications – Perform Mass Additions

System Test Specifications – Add Leased Assets (Optional)

System Test Specifications – Run Depreciation

System Test Specifications – Create Journal Entries and Reconcile to the General Ledger

System Test Specifications – Perform Cost and Depreciation Life Adjustments

System Test Specifications – Capitalize CIP Assets

System Test Specifications – Reclassify Assets

System Test Specifications – Retire and Reinstate Assets

System Test Specifications – Transfer Assets

System Test Specifications – Run Depreciation

System Test Specifications – Create Journal Entries and Reconcile to the General Ledger

System Test Specifications – View Financial Information

System Test Specifications – View Transaction History

System Test Specifications – Run Depreciation Projections

System Test Specifications – Perform Mass Transactions

System Test Specifications – Run Reports

System Test Specifications – Tax book transactions

Data Profile - <Scenario Number>

Defect Log

Open And Closed Issues For This Deliverable

Open Issues

Closed Issues

Note:To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Document Controlii

FixedAssets

File Ref: Fixed-Assets-Test-Script.doc (v. DRAFT 1A)

Doc Ref: <Document Reference Number>

TE.040 System Test Script

XXX 0, 0000

Overview

This System Test Script documents the steps needed to test the integration of application extensions with the target application system with respect to the <Process> process.

System testing measures the quality of the entire application system, using system test sequences and scripts. You must create scripts for all business processes based on the Mapped Business Requirements (BR.030). You should be able to reuse the test scripts you created during Test Business Solutions (BR.080); however, the focus of business solution testing is confirming individual business processes, while business system testing focuses on confirming the collective application system. For more information, refer to Business Mapping Test Results (BR.080) as a basis for business system test specifications.

This system test will include the following types of testing:

Integrated Business Processes
Manual Procedures
Support Procedures
Security Testing
Initial System Documentation Inspection
Manual Data Inspection
Database Journaling
Converted Data Load Testing
Converted Data Inspection
Interface Testing (limited to processing data as input from another system, or creating data for use by another system)
Data/Transaction Reconciliation to the legacy system
Job Stream Testing (if there is a batch component)
Back-Up and Recovery Testing
Data Archival Testing
Lock Testing Simulating User Load (executing identical scenarios)
Batch Window Test (on full converted data volumes)

Document Controlii

FixedAssets

File Ref: Fixed-Assets-Test-Script.doc (v. DRAFT 1A)

Doc Ref: <Document Reference Number>

TE.040 System Test Script

XXX 0, 0000

System Test Sequences

Note:The tables in this deliverable contain sample data that should be used as an example only. Remove all sample data before completing your final deliverable.

Sequence # / Date / Time / Fixed Assets Test Name / Description / Tester / Test Status / Pass/Fail / Notes
FA10 / 01-01-00 / Add Assets Manually (Detail) / Active / Pass / Test completed successfully
FA20 / Add Assets Manually (QuickAdditions)
FA30 / Add CIP Assets
FA40 / Add Leased Assets (Optional)
FA50 / Perform Mass Additions
FA60 / Run Depreciation
FA70 / Create Journal Entries and Reconcile to the General Ledger
FA80 / Perform Cost and Depreciation Life Adjustments
FA90 / Capitalize CIP Assets
FA100 / Reclassify Assets
FA110 / Retire and Reinstate Assets
FA120 / Transfer Assets
FA130 / Run Depreciation
FA140 / Create Journal Entries and Reconcile to the General Ledger
FA150 / View Financial Information
FA160 / View Transactions History
FA170 / Run Depreciation Projections
FA180 / Perform Mass Transactions
FA190 / Run Reports
FA200 / Tax Book Transactions

System Test Specifications – Add Assets Manually (Detail)

Note:A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:
1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario
2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test
3) Role: Step/Sequence owner
4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information
5) Expected Results: anticipated outcomes or outputs described in measurable terms
6) Actual Results: actual outcomes or outputs described in measurable terms
7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence
8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence
9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

Scenario
Step / Test Step / Role / Action or Path / Expected Results / Actual Results / Expected
Cycle Time / Actual
Cycle Time /
Status
FA10 / 10.1 / Enter a description, an existing category combination. Enter other descriptive information such as tag number, serial number and number of units. / > 1 min. / > 1 min. / Active
FA10 / 10.2 / Enter a current cost for the asset. Verify the date in service, prorate convention, and the depreciation method and life / The prorate convention and the depreciation method and life will default from the asset category. The date in service will default to the system date.
FA10 / 10.3 / Enter units, expense account and location. / The depreciation account in the expense distribution should default from the category setup.
FA10 / 10.4 / Add several assets using the above steps and the following variations:
-Input a prior period asset, including YTD and accumulated depreciation amounts
-Split asset cost to more than one cost center
-Change the depreciation life
-Assign an employee
-Try to save an asset before all required information is input (Required information includes description, category, expense account and location.)
-Input parent asset numbers for child assets
Verify that asset numbers are assigned sequentially. / The system will require that the YTD depreciation be less than or equal to the accumulated depreciation amount
-The system will allow assets to be assigned to more than one cost center by using fractions of a unit
-The system will allow users to change the asset’s depreciation life
-The system will only allow users to input employees that have been setup in the HR tables
-The system will prompt the user for required information before allowing the user to save the asset
-The system will acknowledge if the parent asset number is valid
Asset numbers will be sequential, starting with the next available number as designated in the System Control setup.
FA10 / 10.5 / Add sales tax and overhead allocation to asset lines. Make sure Subledger balances to General Ledger at month end and that appropriate journal entries offset the added lines.

System Test Specifications – Add Assets Manually (Quick Additions)

Scenario
Step / Test Step / Role / Action or Path / Expected Results / Actual Results / Expected
Cycle Time / Actual
Cycle Time /
Status
FA20 / 20.1 / Enter a description, an existing category combination. Enter other descriptive information such as tag number and serial number. / > 1 min. / > 1 min. / Active
FA20 / 20.2 / Assign asset to a Corporate book and input cost, expense account and location / The system will only allow users to select valid expense accounts and valid locations.
FA20 / 20.3 / Repeat the above steps for several assets.

System Test Specifications – Add CIP Assets

Scenario
Step / Test Step / Role / Action or Path / Expected Results / Actual Results / Expected
Cycle Time / Actual
Cycle Time /
Status
FA30 / 30.1 / Enter a description, an existing category combination / Users will be able to enter a description, an existing category combination / > 1 min. / > 1 min. / Active
FA30 / 30.2 / Change the asset type from "Capitalized" to "CIP". / Users will be able to change the asset type from "Capitalized" to "CIP".
FA30 / 30.3 / Assign asset to a Corporate book and input cost, expense account and location / The system will only allow users to select valid expense accounts and valid locations.
FA30 / 30.4 / Repeat the above steps for several assets

System Test Specifications – Perform Mass Additions

Scenario
Step / Test Step / Role / Action or Path / Expected Results / Actual Results / Expected
Cycle Time / Actual
Cycle Time /
Status
FA40 / 40.1 / Enter a lease number, description, lessor, lease type and term month in the Lease Details form. / The system will not allow users to input lessors which have not been setup as suppliers. / > 1 min. / > 1 min. / Active
FA40 / 40.2 / Enter a leased asset in the Asset Workbench. / Users will only be able to input valid category and asset key combinations.
FA40 / 40.3 / Choose a lease number from the List of Values. / The system will not allow users to input lease numbers that have not been setup in the system.
FA40 / 40.4 / Enter a current cost for the asset. Verify the date in service, prorate convention, and the depreciation method and life. / The prorate convention and the depreciation method and life will default from the asset category. The date in service will default to the system date.

System Test Specifications – Add Leased Assets (Optional)

Scenario
Step / Test Step / Role / Action or Path / Expected Results / Actual Results / Expected
Cycle Time / Actual
Cycle Time /
Status
FA50 / 50.1 / Create invoices for Fixed Asset purchases and charge them to the Asset Clearing account. Approve invoices and post to the General Ledger and Run the Mass Additions Create Program.
Oracle Payables / The approval and posted statuses will be change to "Yes" in Oracle Payables.
The Mass Additions Create program will populate the Mass Additions interface table in Oracle Assets / > 1 min. / > 1 min. / Active
FA50 / 50.2 / Open the Prepare Mass Additions form
Mass Additions  Prepare Mass Additions / The Find Mass Additions form will open.
FA50 / 50.3 / Choose the invoices in the Find Mass Additions form verify that the invoices input in Purchasing/Payables were successfully imported into Oracle Assets. / Oracle will display all the Mass Addition entries for the chosen invoices in the Prepare Mass Additions form.
FA50 / 50.4 / Add category, expense distribution, location and asset key to several invoice lines in the Prepare Mass Additions form.
(B) Open / The system will not permit users to input invalid categories, expense distributions, locations or asset keys.
FA50 / 50.5 / Merge some invoice lines together to create a single asset. Perform the merge function at least twice.
(B) Merge / Users will be able to merge invoice lines. The system will assign the merged lines a queue status of "Merged".
FA50 / 50.6 / Undo one of the merges performed in Step 50.5
(B) Undo Merge / Users will be able to reverse merged lines before the parent invoice line is posted.
FA50 / 50.7 / Split some invoice lines into more than one line.
(B) Split / Users will be able to split invoice lines. The system will assign the split lines a queue status of "Split".
FA50 / 50.8 / Undo one of the splits performed in Step 50.8
(B) Undo Split / Users will be able to reverse split lines before the split children are posted.
FA50 / 50.9 / Add an invoice line to a CIP asset:
- Select an invoice line to add to a CIP asset
- Select the "Add to Asset" button
- Select a CIP asset to add the invoice line to
Select the "Done" button
(B) Add to Asset / Users will be able to add invoice lines to CIP assets.
FA50 / 50.10 / Change the queue name to "Post" for each line that is capitalizable.
For a few invoice lines, change the queue name to "Delete".
(B) Open / The system will change the queue name to "Cost Adjustment" for all invoice lines that were added to an asset.
FA50 / 50.11 / Post Mass Additions
Mass Additions  Post Mass Additions / The program will post all invoice lines with a queue status of "Post" or "Cost Adjustment" to the FA tables. After the program completes, the queue status for these invoice lines will change to "Posted" in the Prepare Mass Additions form
FA50 / 50.12 / Review the Mass Additions Exception Report and Posting Report / The Mass Additions Posting Report will detail all the invoice lines posted in Step 50.11
FA50 / 50.13 / Verify that the assets posted properly.
Assets  Asset Workbench / Users will be able to view all the assets created in Step 50.11.
FA50 / 50.14 / Run the Delete Mass Additions program / The program deletes all invoice lines in the Prepare Mass Additions form with a queue status of "Delete".
FA50 / 50.15 / Review the Mass Additions Delete Report / The report will detail all the invoice lines deleted in Step 50.14.
FA50 / 50.16 / Verify that invoices marked as "Delete" are no longer in the Prepare Mass Additions form / The invoice lines deleted in Step 50.14 will no longer appear in the Prepare Mass Additions form