Acceptance Tests and Outcomes

BRD Ref

Test Scenario and Acceptance Criteria

Date Tested

Tested By

Test Outcome

1.1

Payment data to be automatically downloaded from the various ‘pathways’ on the WPM ftp site overnight.

N.B. that the WPM ftp site has multiple ‘pathways’ for the different types of payments awaiting download, some generic and some customised for specific applications – the interface developed by this project must be flexible enough to cater for these multiple pathways and the addition of new pathways in the future

1.2

Email to be sent to FIS if no files to download.

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. no files found)

1.3

Email to be sent to FIS if errors occur during the download.

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. error during download from WPM ftp site)

1.4

Copy of downloaded data to be kept for audit purposes

1.5

Downloaded files that have been successfully loaded into eFinancials should be automatically deleted after 70 days.

1.6

Downloaded data to be validated to ensure that the contents of the batch agree to the batch header, both in terms of quantity and value.

1.7

Email to be sent to FIS if errors occur during the validation.

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. validation error during download from WPM ftp site)

1.8

Data to be loaded into the eFinancial CLINK tables

1.9

Summary report to be e-mailed to FIS, confirming the total value and number of records posted to CLINK.

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. WPM data successfully loaded to CLINK)

Mail text for phase 1 to indicate that manual posting is required.

Mail text for phase 2 to indicate that automatic posting will take place.

1.10

The download must be capable of recovering from errors with minimal intervention.

BRD Ref

Test Scenario and Acceptance Criteria

Date Tested

Tested By

Test Outcome

2.1

Manual journal files to be automatically collected from a ‘pickup area’ at specified intervals (e.g. hourly/daily)

2.2

The ‘pickup area’ must be somewhere accessible to FIS and other nominated School staff so that they can drop files there that need loading into eFin. 

2.3

The ‘pickup area’ must be accessible for other applications, so that they can deposit journal files for automatic uploading via this new process

2.4

Users must not be able to view or amend other users’ files

2..5

Invalid/unrecognised file names to be reported to FIS via e-mail

2.6

Basic validation to be carried out on files (number of records and total = header)

2.7

Email to be sent to file owner if errors occur during the validation.

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. validation error during loading of journal file x).

2.8

Summary report to be e-mailed to FIS, confirming the total value and number of records in the file

2.9

Copy of files to be kept for audit purposes

2.10

Files that have been successfully loaded into eFinancials should be moved into an archive area, then automatically deleted after 70 days.

2.11

If not already present, a unique reference number to be applied to the file.

2.12

Validated data to be loaded into the eFinancials CLINK tables

2.13

Summary report to be e-mailed to FIS, confirming the total value and number of records posted to CLINK..

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. WPM data successfully loaded to CLINK)

Mail text for phase 1 to indicate that manual posting is required.

Mail text for phase 2 to indicate that automatic posting will take place.

BRD Ref

Test Scenario and Acceptance Criteria

Date Tested

Tested By

Test Outcome

3.1

Files to be posted from CLINK to eFinancials General Ledger at specified intervals e.g. hourly/daily (if relevant accounting period is open)

3.1.1

Generated files will include separate lines for each transaction or item contained within a transaction where appropriate, plus a corresponding control account entry.

3.2

Only file types specified in the Control Mechanism (detailed in the section below) will be posted

3.3

Standard ABS routines to be used wherever possible (e.g. CLIR02)

3.4

The General Ledger to be interrogated to determine whether the posting was successful or not – this information to be used to determine the wording of the e-mail described on the line below.

3.5

Report produced by ABS routine to be e-mailed to FIS

Mail title to include the environment (e.g. Dev/Test/Live) and the nature of the e-mail (e.g. report from CLIR02).

There should be a differentiation between the titles of mails containing error reports and those containing success reports.

BRD Ref

Test Scenario and Acceptance Criteria

Date Tested

Tested By

Test Outcome

4.1

Facility to switch the interface on & off to control which accounting period the data is posted to (e.g. at month end)

4.2

Facility to allow the restriction of specific WPM CPG pathways/file names e.g. B&B payments to be suspended but Delegate Registration payments allowed through.

4.3

Facility to add new WPM CPG pathways or manual file names for downloading

4.4

Facility to amend existing WPM CPG pathways or manual file names including the facility to amend: -

• Frequency
• E-mail address for error/success reports

4.5

Facility to delete WPM CPG pathways or manual file names no longer required

4.6

Each entry to include the following information: -

• Pathway/file name
• Control account (cost centre/account code/job code)
• VAT account (cost centre/account code/job code)
• Prefix for unique reference
• e-mail address to send error reports to
• on/off flag
• frequency

4.7

Control Mechanism only to be accessible to in FIS

BRD Ref

Notes on Test and/or Test Outcome

Ref

Test Scenario and Acceptance Criteria

Tested By

Date Tested

Outcome (PASS / FAIL)

 Duplicate files

 Recovery from error – invalid file content

Ref

Notes on Test and/or Test Outcome

BRD Ref

JIRA Test Log Ref

Issue Summary

Impact on UAT Sign Off

Project Manager

Name

Date Signed Off

Project Sponsor

Name

Date Signed Off

Business Analyst

Name

Date Signed Off

Add other signatories here