Acceptance Tests and Outcomes

Test Case 01: IDM to Alma feed successful

Pass/Fail

Test Description:  The feed between IDM and Alma runs successfully

Date tested:

Tested by:  Alex Forrest

Preparation: Re-confirm with HR and Student systems that we can move the identity feed to use IDM (req 1.5)

Prep complete/not complete

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

1.1

1.1

(SDS 4.1.2)

M

The new library system allows updates from IDM patron data

Zip files containing XML user files are placed at the defined S/FTP location where they are fetched and uploaded by Alma

1.2

1.4

M

Library receives the period bulk load of patron data from IDM on a weekly basis

1.3

1.2/SDS 4.1.4

SH

Library can amend the cron job If the running frequency needs to be changed

(there is no need to change the IDM Lib App itself)

1.4

1.2

SH

Library receives on demand changes via web services to patron data from IDM twice a day (initially)

Can be done in two ways

• IDM Lib App can be invoked either manually
• automatically by a cron job

Ensure Library can utilise both methods

N/A

Not to be tested – future changes – only bulk load included SDS 4.1.4

1.5

1.3

SH

For on demand changes via web services only, periodically synchronise the data between both systems to avoid any support issues with failed changes

N/A

Not to be tested – future changes – only bulk load included

Test Case 02: IDM to Alma feed unsuccessful

Pass/Fail

Test Description:  The following error scenarios should be tested should the feed be unsuccessful. The error reports were not part of the BRD but have been included in the design

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

2.1

SDS 4.1.2

Error reports: Zip generation – error email: if the compressed Zip file cannot be generated, an error email will be reported -  this will stop the batch process

2.2

SDS 4.1.2

Error reports: SFTP transfer – error email: if the Zip file cannot be transferred, an error email will be reported -  this will stop the batch process

2.3

SDS 4.1.2

Error reports: Retrieving IDM data – warning email: for each batch run, if certain UUNs cannot be retrieved, a warning email contains failed UUNs will be reported - this will not stop the batch process

Test Case 03: Patron data

Pass/Fail

Test Description:  This will test that the correct identities will be available to Alma from IDM

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

3.1

2.1.1

M

IDM sends the identity of  post-graduate research student to the library system

3.2

2.1.1

M

IDM sends the identity of  post-graduate taught student to the library system

3.3

2.1.1

M

IDM sends the identity of  undergraduate student to the library system

3.4

2.1.1

M

IDM sends the identity of  staff to the library system

3.5

2.1.1

M

IDM does NOT send the identities of functional, applicant and alumni to the library system  - they are not required by Library

3.6

2.1.2

SH

IDM sends the identity of  visiting staff and visiting student to the library system

Not to be tested – this will be in future development. Issues with email addresses and card connector

Test Case 04: Patron data scenarios

Pass/Fail

Test Description:  This will test the different scenarios as laid out in the mapping exercise under requirement 2.3

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

2.3

One active affiliation

4.1

If a member of staff has only one active affiliation then that affiliation is sent in the IDM to Alma feed

4.2

If a student has only one active affiliation then that affiliation is sent in the IDM to Alma feed

4.3

If a member of staff has only one affiliation and this affiliation currently expiring in IDM, it will be sent in the IDM to Alma feed until one month after the expiry date

4.4

If a member of staff has only one affiliation but this affiliation is expiring in IDM it will be not be sent in the IDM to Alma feed if expiry date plus one month is reached

More than one affiliation – all active

4.5

If a member of staff has more than one affiliation then the affiliation with the highest value is sent to the IDM to Alma feed (e.g. STF > STUPGR)

4.6

If a student has more than one affiliation then the affiliation with the highest value is sent in the IDM to Alma feed (e.g. STUPGR > ALUM)

more than one affiliation – not all active

4.7

If an identity has two affiliations in IDM and  only one of the affiliations is active (affiliation 1) and the other is not (affiliation 2 either Suspended or Deleted) then only the active affiliation (affiliation 1)  is sent in the IDM to Alma feed

Expiry– Test that identities are sent in the IDM to Alma feed if they are not due to expire and that they are not sent to in the feed if they have expired

4.8

If an identity (staff or student) has more than one active affiliation then the expiry date is mapped to the affiliation that has the longest affiliation end date.

For example, identity has affiliation 1 and affiliation 2,

affiliation 1 > affiliation 2, however affiliation 2 ends on 31/12/2016, whereas affiliation 1 ends on 31/12/2015

therefore "affiliation 1 with expiry date 31/12/2016" is sent to the library

Test for both staff and student

Ensure correct end of course date for students

Still in discussions PGR and PGT?

4.9

UG Students: - 120 days + 1 month

4.10

PGT Students: - 120 days + 3 month

4.11

PGR Students: - 180 days + 3 month

Test expiry

4.12

UG Students: Primary active affiliations will be sent in the IDM to Alma feed up to one month after expiry date

4.13

UG Students: Primary active affiliations will NOT be sent in the IDM to Alma feed one month after expiry date

Test exactly 1 month and more than 1 month

4.14

PG Students: Primary active affiliations will be sent in the IDM to Alma feed up to one month after expiry date

4.15

PG Students: Primary active affiliations will NOT be sent in the IDM to Alma feed one month after expiry date

Test exactly 1 month and more than 1 month

4.16

UG Students with no End date in IDM will be sent in the IDM to Alma feed if their SA38_EST_STUDY_ENDDATE date in EUGEX + 1 month is not reached

4.17

UG Students with no End date in IDM will not be sent in the IDM to Alma feed if SA38_EST_STUDY_ENDDATE date in EUGEX + 1 month is reached

Test exactly 1 month and more than 1 month

4.18

PG Students with no End date in IDM will be sent in the IDM to Alma feed if their SA38_EST_STUDY_ENDDATE date in EUGEX + 3 month is not reached

4.19

PG Students with no End date in IDM will not be sent in the IDM to Alma feed if SA38_EST_STUDY_ENDDATE date in EUGEX + 3 month is reached

Test exactly 3 months and more than 3 months

4.20

Staff on permanent contract will be sent in the IDM to Alma feed until the end of their contract

(Their expiry date is set as end of contract)

purge date and expiry date are the same and equal to [load date + five years]

4.21

Staff on permanent contract will not be sent in the IDM to Alma feed if their end of contract is reached

(Their expiry date is set as end of contract)

4.22

Staff where there is no end of contract will be sent in the IDM to Alma feed until their expiry date is reached

(Their expiry date is the same as the purge date and the [load date + five years])

4.23

Staff where there is no end of contract will not be sent in the IDM to Alma feed if they have reached their expiry date

((Their expiry date is the same as the purge date and the [load date + five years])

More than one affiliation – all expiring

4.24

If an identity has multiple affiliations in IDM, and all of the affiliations are expiring then only the ‘highest’ affiliation is sent in the IDM to Alma feed only if the load date is less than 1 month after the expiry date,  otherwise this identity will not be processed in the load.

Test start dates

4.25

Start dates are taken from the highest affiliations start date

4.26

Address end date will take expire date

Addresses

4.27

The address format is readable

4.28

Staff address will be work address

(from IDM)

4.29

Student address will be the term address

 (from IDM/Eugex)

Stats Category

4.31

The notes field has been moved to the Statistical category page and the Library can view Stats category notes in the form:

Org:UoE:College of Humanities and Social Science:College of Humanities and Social Science:Business School:BUS

Other

4.32

OLL Students will not be sent in the IDM to Alma feed

4.32

Library card number/bar code is available for each record

Test Case 05: Account suspension

Pass/Fail

Test Description:

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

5.1

4.1/SDS 4.1.6

M

For account suspension Library can make an account inactive (determined on purge_date)

Following rules are successful :

• For all students and staff with expiry date already known, set purge_date as  [expiry_date + 2 years]

• For Staff that has no end date in IDM, both expiry and purge dates will be set to [load date +5 years].

5.2

4.2

M

For deleted accounts Library can make an account

• Active for a grace period,
• Inactive for a set period
• then Deleted (from the load)

(in line with University’s data retention policy)

5.3

4.2

M

Library can control deletion of local data as there may be instances where a patron had outstanding fines/fees and items issued

If suspended in IDM, this will not be sent to Library. Library does not care about the S status.

Is this all identities?

CHECK

Test Case 06: MyEd Channel updated

Pass/Fail

Test Description:

Date tested:

Tested by:  Alex Forrest

Paul Johnson, Web Interfaces Team Manager, used web statistics to see which links from the original channel were used the most in order to prioritise their inclusion in the channel. His design mockup for MyEd channel can be found at https://www.wiki.ed.ac.uk/display/mockups/MyEd+Library+Channel and the items listed below reflect this design.

From the BRD items have therefore not been included i.e. 5.4.2; 5.4.3; 5.4.4; 5.4.6; 5.4.9 – or are these covered under advanced search? TBD

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

6.1

5.1

M

The existing Library channels should be accessed through single sign-on

6.2

5.2

M

The existing Library MyEd Search, Accounts and Resources channels to Voyager should integrate with ALMA

6.3

5.3

M

Users can make a generic search from the Library Channel using search terms and keywords

6.4

5.4.8

M

From the channel users can access Library Resources – the Library homepage

6.5

5.3.5

M

From the channel users can access Library Resources – Exam Papers Online

6.6

5.3.3

M

From the channel users can access Library Resources – Databases A-Z

6.7

5.4.10

M

From the channel users can access Library Resources – Interlibrary Loans

6.8

NEW LINK

From the channel users can access Library Resources – Centre for Research Collections (CRC)

6.9

NEW LINK

From the channel users can access Library Help – Locations and opening

6.10

5.4.7

M

From the channel users can access Library Help – Service Status & Alerts

6.11

5.4.5

M

From the channel users can access Library Help –IS Helpline link

6.12

4.5.11

M

From the channel users can access Library News – the Library blog

6.13

New

From the channel users can Like the Library under Library News

6.14

New

From the channel users can Follow the Library on Twitter under Library News

6.15

New

From the channel users can access icons for Wordpress, Facebook and Twitter

6.16

5.4.1

M

There should be a link to Learn more about DiscoverEd

6.17

5.5

M

Users should be able to return to their MyEd Dashboard from the Search channel

Test Case 07: Users can see their own account details in MyEd

Pass/Fail

Test Description:

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

7.1

5.6.4

M

Users can login to their Library Account from the Library channel

7.2

5.6.1

M

My Account channel should display total number of items on loan for user

7.3

5.6.1

M

On selecting Items on loan user can see a breakdown by Item, Type, Status, Due Date

7.4

5.6.2

M

My Account channel should display total number of requests for user

7.5

5.6.2

M

On selecting Requests user can see a breakdown by item, Pickup location, Status

7.6

5.6.3

M

My Account channel should display total number of Fines/Fees for user

7.7

5.6.3

M

On selecting Fines/Fees user can see a breakdown by Item, Type, Status, Due Date

7.8

5.6.5

M

Users can return to their MyEd Dashboard from the Account channel

Test Case 08: Users not part of the university can access the Library system

Pass/Fail

Test Description:  Will test that non UoE staff such as NHS can access the university libraries in order to borrow books

Date tested:

Tested by:  Alex Forrest

TEST ID

BRD ref

P

Test scenario and expected outcome

Pass/Fail

Comments

8.1

6.1

M

Users not part of the university (such as NHS staff) can access the new Library system and borrow books from the university libraries.

Ref

Test Scenario and Acceptance Criteria

Tested By

Date Tested

Outcome (PASS / FAIL)

Ref

Notes on Test and/or Test Outcome

BRD Ref

JIRA Test Log Ref

Issue Summary

Impact on UAT Sign Off

Project Manager

Karen Stirling

Date Signed Off

Project Sponsor (Senior Business User on behalf of Sponsor)

Laura M Shanahan

Date Signed Off

Business Analyst

Sue Woodger

Date Signed Off

Business Area Manager

Alex Forrest

Date Signed Off