Acceptance Tests and Outcomes

BRD Ref

Scenario / Acceptance Criteria

Tested By

Date Tested

Outcome (PASS / FAIL)

 1.1

The originator can submit the staff request without selecting the University of Edinburgh from the default company field. 

 PASS

 1.2

 PASS

 1.7

1. If the originator has entered fixed term Years and Month the target end date should be calucualted based on teh start date wehn this is entered in teh back office.

2. If the originator has entered a fixedx term ending date then this should feed into the target end date, regardless of the start date enterec

3. The recruiter can manually update the target end date if required once the fixed term duration has been calculated.

4. The target end date should be correct based on the start date and the selected fixe term years and months

5. The UOE developer can see the calculated or manually entered target end date in the views.

 PASS

1. The originator can entere the years and months appropriate for the fixed term duration position if the employment category is fixed term.

2. The originator can enter the years and months appropriate for the fixed term duration position if the employment category is HTBN or HTBN summer

3. The originator cannot submit a staff request without entering EITHER the fixed term end date or Fixed term years and months if they have selected fixed term end date and fixed term duration in years and months

4. The originator cannot enter both a fixed term end date and fixed term duration in years and months

5. The originator cannot select the years and months appropriate for the fixed term duration position if the employment category is open ended

6. The originator cannot enter a alpha value in to the Fixed Term Duration field (i.e. only numeric values are accepted)

1. The recruiter can slect a vacancy within the web applicant screens and "select all " before selecting "update" to accept all applications into the back office.

2. Once completing step 1, the recruiter can then select a different vacancy and has the option to "select all" before selecting "update"

1. The recruiter should be able to veiw a list of notificaitons snet to an applicant  if they right click on the applicant in the applicant details screen in the back office. (Note: This list will not include autogenerated notifications, only those requiring manual input)

2. The list of notifications shown to the recruiter is correct for that applicant

3. The recruiter can selct the notification shown in the pop up (after right click) and open the notificaiton to view a copy of the email.

1. PDFs generated from the merge applications functionality should include a divider (blank page) between each application

All other test scenarios for PDF are included under 4.2

1. An approver should have an option under the My Approvals section that will allow them to view all apporved, rejected (and outstanding?) staff requests for their departments

2. an approver should see all approved, rejected (and outstanding?) staff requests for their departments  that are assigned to their user access (under user managment)

3. An approver should see the correct number and status of staff requests for their department(s)

1. The applicants initials that are input on the "initials" field in the applicant personal details section fo the applicant portal should be available to add as a mail merge field to notifications.

2. The applicants initials that are input on the "initials" field in the applicant personal details section of the applicant portal should be populated in to the application screens in the back office.

3. The applicants initials that are input on the initials  field in the applicant personal details section of the applicant portal should be populated in the application screens of the recruiter portal.

4. The data shown on the notifications, back office and recruiter portals should be as entered by the applicant in the initals field on the applicant portal

5. The applicant should be able to ammend their initials and this data be udpated in the views, back office and recruiter portals.

1. The applicant should only receive notificaitons for criteria selected, i.e. if they select grade 6 they should not recieve notifications for grade 7

2. The applicant should only receive notifications hat match all criteria they select

3. The applicant should be able to change the notifications they recieve

4. The applicant should be able to select more than one option from each group of criteria ie.grade 6, 7,8

1. The applicant should be able to select and confirm an interviewslot from those available

2. Once selected the interview slot should not be available for another applicant to select.

3. The applicant should be provided with an acknowledgement hat the selection of the interview slot has been sucessful (either via a popup or email - CORE to confirm)

1. An internal applicant that does not have a valid email address held in IDM/IDM views should be returned a message to alert them to contact HR systems team as the data held against them is incomplete

2. An internal applicant that registers successfully should be returned an on screen message that includes the email address that is held against that UUN in IDM/IDM views.

EM 1/5 - The sepecification discussed and used for development did not call for a notification to be created (for no 2 above). Functionality which is currently in software re notification will be what is displayed.

1.The recruiter should be able to generate a single appolication pdf via the back office

2. the recruiter should be able to generate an application pack, which should included all selected applications for a vacancy via the back office

3. The recruiter should be provided alerts to confirm that the generation process has started, and recieve an email to confirm the process has completed

4. The PDF genreation process shoud take no longer than 20 mins from start to finish (this is worst case scenario for a large PDF at a busy time!)

5. The pdf's generated should be output in font 11 or bigger

6. the pdf's should include a page divider where multiple applications are generated

7. The pdf generation process should not stop when a corrupt or password protected docutment is included as part of the application pack

8. It should be possible to generate pdfs of different file format, specifically .doc, pdf, jpeg

EM1/5 - the majority of the items flagged above will come with teh Aspose software installation as standard, however the remit of the Asposse softare installation was to implement this as it provide a far more robust solution than what was there previously. Specific modifications were not made for UE re. Aspose. I would not see an issue with the above listed items 1- 8, however where no 5 specifies a specific font size, the software will need to be tested to see if the standard output reflects this.

The originator can enter the data for;

1. Advertiser Contact name (free text)

2. Advertiser Contact number (numeric free text)

3. Advertiser Contact email (free text)

4. Closing Date in Weeks (drop down - 1,2,3,4)

note: this is a free text field, not a drop down field.

In specific fields:

Detials entered in to the the staff request for the fields should feed into the vacnay maintenance screen in the back office onc ethe staff request has been approved;

1. Advertiser Contact name feeds into contact perons

2. Advertiser Contact number feeds into phone

3. Advertiser Contact email feeds into email

4. Closing date in weeks (new field BO)

The UOE developer can see the fields and the correct data relating to;

1. Advertiser Contact name (free text)

2. Advertiser Contact number (numeric free text)

3. Adverister Contact email ( free text)

4. Closing date in weeks (drop down - 1,2,3,4)

In the views for adding to the BOXI universe

1. An originator cannot submit a staff request where they have selected "Post required to be advertised" without entering advert text AND further particulars and selecting an applicaiton form

2. An originator cannot submit a staff request where they have selected "post is required to be advertised" entered advert text BUT NOT further particulars

3. An originator  cannot submit a staff request where they have selected "Post  is required to be advertised" entered further particulars BUT NOT advert text

4. An originator cannot submit a staff request where they have selected "Post is required to be advertised" entered further particulars AND advert text but have NOT selected an application form

5. An originator can submit a staff request where they have selected "Post is required to be advertised" and entered advert text and further particulars and selected an application form.

6. An oringator has selected "Post requried to be advertised" and can submit the staff request without entering advert text. further particulars, or to select an application form.

7. An originator has selected "Post required to be advertised" and can submit the staff request with advert text, further particulars or to select an application form.  

1.An originator can enter te advertiser name in to the "other" field and submit staff request

2. A system administrator can set up a process and notificaiton to trigger a notification on approval of the staff request with mail merge fields for the details of the text entered into "other" and the staff request ID in the notificaion

3.A system notificaiton is triggered on approval of the staff request to the system administrator

4. System administrator can update the advertiser profile in the back office to add any new advertisers

5. An originator can select any "new" advertisers on the staff request for subsequent staff requests

1. The recruiter should be able to view a list of notifications sent to an applicant if they right click on the applicant in teh applicant details screeen in the back office.

2.The list of notifications shown to the recruiter shown in the pop up (after the right click) and open the notification to view a copy of that email.

3. The recruiter can select the notification shown in the pop up (after the right click) and open the notification to view a copy of that email.

1. A recruiter in X department searches for an applicant in the back office. They should only be returned details of applicants who have applied for vacancies in X department.

2. A recruiter in department X who has completed an applicant search (criteria 1) should only be able applications relating to vacancies in department X for applicants that have applied for a vancancies in departments z and y.

Note: Department X,Y and Z relates to the users security access profile

1. System administrator can add a "flag" on a users profile

2. System administrator can update the user profile to correspond witha  users training record.

3. Flags are viewablein the Boxi universe

4. When the user profile flag is updated in eRecruitment this is correctly updated in Boxi

1. System administrator can add a "flag" on a users profile

2. System administrator can update the user profile to correspond with a users training record

3. Flags are viewable in Boxi

4. When the user profile flag is updated in eRecruitment this is correctly updated in BOXI

1. System administrator can amend the additional question to include a non applicable option.

2. Applicants have the option to select N/ A for th addtional question relating to migrant workers

3. The sucessful applicant interface can handle the N/A option to ignore this and only transfer yes/no responses to Oracle. N/A should be returned as a blank field to Oracle

1. An applicant can select to receive updates as a single daily notification on their “My Account” section.

2. Ann applicant can choose to receive vacancy updates, that match their criteria, as and when vacancies are posted.

3. If an applicant has selected daily notifications then they should only receive a single daily update for any notifications posted in the agreed Daily period (Core to confirm this period, i.e. is this 12 – 12 the previous day).

4. Applicants who have not selected the daily update option in My Account should receive notifications that match their criteria when each vacancy goes live.

1. A system administrator can create an new additional question to collect student matriculation numbers.

2. This new additional question field can be viewed by a UoE developer in the eRecruitment Views (for adding to BOXI)

1. The successful applicant interface view is updated to include the student matriculation number collected from the applicant in the additional questions section.

2. If an applicant has entered a matriculation  number this is transferred during the successful applicant transfer process to the “matriculation number” on the additional personal details screen in Oracle.

BRD Ref

Notes on Test and/or Test Outcome

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

Name

Date Signed Off

Project Sponsor

Name

Date Signed Off

Business Analyst

Name

Date Signed Off

Add other signatories here