Supply and Installation of Integrated Front Office

Service Delivery Platform

UAT-User Acceptance testing

Integration Layer with ESB

UAT-User Acceptance Testing

 UAT-User Acceptance testing

TC-GG01 - User authentication

The ADISA IFO system will authenticate and authorize its users using the enterprise single sign-on of GG federation.

PRIMARY ACTOR CONFIGURATIONS

Every user in the system. User accounts are created in the system.

PRECONDITIONS SUCCESS GUARANTEES

Communication of IFO system and GG will be based on WS-federation The user is successfully authenticated using GG ADFS method.
and WS security protocol.
The IFO System is configured as a trusted relying party on GG.
The GG Federation Provider has configured four Identity Providers,
one of them is the Government Employees Identification (GOV ADFS).

User authentication
User authentication Test Scenario Procedure/Inputs Expected Results Pass/Fail
1. User selects the login method (Internal User selects the login methods. The system displays the login
or External user) methods: (Internal or External user)
2. User selects to login as an External user. User clicks the “External user" button. IFO system redirect the user to the
GG interface.
3. User provide credentials to GG interface User provide credentials to GG interface The system displays username and
(username, password). (username, password). password fields.
4. GG authenticate the user. User click the "Log in" button. GG authenticate the user.
5. User login in the system. User login in the system.
6. User access the system functionalities User access the system functionalities The system displays system
based on its role. based on its role. functionalities based on user roles.

Extensions Procedure/Inputs Expected Results Pass/Fail

2.a User selects to login with Internal User clicks the “Internal user" button. The system displays username and
Identity Provider password fields.
Page 1
 UAT-User Acceptance testing

1. User submit username and User submit username and password. The system validates username and
password. password.
2. If the user login for the first time, User click the "Log in" button. The system sends automatically a
the system sends automatically a login code to the user email
login code to the user email address. address.

3. User submit login code. User submit login code. The system validates the login code.
4. Use case continuo at step 6
Extensions Procedure/Inputs Expected Results Pass/Fail
4.a GG doesn't authenticate the user.
1. The system displays a message User clicks "GG ADFS" button. The system displays a message
"Identification in the portal can't be "Identification in the portal can't be
done. Please submit the right done. Please submit the right
username and password". username and password".
2. The use case continuo at step 3.

Testing summary and Signatures

Time of start Time of finish

Results: Successful, without problems

Successful, with notes
Not successful:

Choose problem priority with biggest priority:  P1  P2  P3

Additional tests will be done on: Time:

Page 2
 UAT-User Acceptance testing

Notes and suggestions:

Company Institution Institution

Tester Inspector Inspector

Signature: Signature: Signature:

TC-GG02 - Integrate with NCR system

PRIMARY ACTOR
Front Office Clerk

PRECONDITIONS SUCCESS GUARANTEES

Front Office Clerk is successfully logged in the system with its own The system is successfully integrated with NCR.
credentials.
GG, IFO system DIS, NCR DIS is up and running.
IFO system account in GG has permissions to consume personal data
service.

Integrate with NCR system

Integrate with NCR system Test Scenario Procedure/Inputs Expected Results Pass/Fail
1. Front Office Clerk searches for citizen Front Office Clerk submit citizen NID and The system is integrated with NCR
data using citizen NID clicks the "get data" button. system and display citizen data like
name, surname, father name,
birthday, birthplace, gender,
address.
Page 3
 UAT-User Acceptance testing

Extensions Procedure/Inputs Expected Results Pass/Fail

1.a The integration with NCR system is not
possible.
1. Front office clerk submit the Front Office Clerk submit citizen NID and IFO system display a message type:
wrong NID format. clicks the "get data" button. “The identification number is not in
the right format. Please verify the
identification number.”
2. Front office clerk submit the Front Office Clerk submit citizen NID and IFO system display a message type:
wrong NID. clicks the "get data" button. “No data found for this
identification number”.

Testing summary and Signatures

Time of start Time of finish

Results: Successful, without problems

Successful, with notes
Not successful:

Choose problem priority with biggest priority:  P1  P2  P3

Additional tests will be done on: Time:

Notes and suggestions:

Company Institution Institution

Page 4
 UAT-User Acceptance testing

Tester Inspector Inspector

Signature: Signature: Signature:

TC-GG03 - Integrate with NBC system

PRIMARY ACTOR
Front Office Clerk

PRECONDITIONS SUCCESS GUARANTEES

Front Office Clerk is successfully logged in the system with its own The system is successfully integrated with NBC system.
credentials.
GG, IFO system DIS, NBC DIS is up and running.
IFO system account in GG has permissions to consume personal data
service.

Integrate with NBC system

Integrate with NBC system Test Scenario Procedure/Inputs Expected Results Pass/Fail
1. Front Office Clerk searches for subject Front Office Clerk submit citizen NUIS and The system is integrated with NBC
data using citizen NUIS. clicks the "get data" button. system and display subject data like
name, surname and NID of
administrator, subject name,
judicial form, state, registration
date, address.

Extensions Procedure/Inputs Expected Results Pass/Fail

1.a The integration with NBC system is not
possible.
1. Front office clerk submit the Front Office Clerk submit citizen NUIS and IFO system display a message type:

Page 5
 UAT-User Acceptance testing

wrong NUIS format. clicks the "get data" button. “The identification number is not in
the right format. Please verify the
identification number.”
2. Front office clerk submit the Front Office Clerk submit citizen NUIS and IFO system display a message type:
wrong NUIS. clicks the "get data" button. “No data found for this
identification number”.

Testing summary and Signatures

Time of start Time of finish

Results: Successful, without problems

Successful, with notes
Not successful:

Choose problem priority with biggest priority:  P1  P2  P3

Additional tests will be done on: Time:

Notes and suggestions:

Company Institution Institution

Tester Inspector Inspector

Signature: Signature: Signature:

Page 6
 UAT-User Acceptance testing

TC-GG04 - Integrate with GDT system

PRIMARY ACTOR
Front Office Clerk

PRECONDITIONS SUCCESS GUARANTEES

Front Office Clerk is successfully logged in the system with its own The system is successfully integrated with GDT system.
credentials.
GG, IFO system DIS, GDT DIS is up and running.
IFO system account in GG has permissions to consume personal data
service.

Integrate with GDT system

Integrate with GDT system Test Scenario Procedure/Inputs Expected Results Pass/Fail
1. Front Office Clerk searches for subject Front Office Clerk submit citizen NUIS and The requested data are not found in
data using citizen NUIS. clicks the "get data" button. NBC system, so the system is
integrated with GDT system and
display subject data like name,
surname and NID of administrator,
subject name, judicial form, state,
registration date, address.

Extensions Procedure/Inputs Expected Results Pass/Fail

1.a The integration with GDT system is not
possible.
1. Front office clerk submit the Front Office Clerk submit citizen NUIS and IFO system display a message type:
wrong NUIS format. clicks the "get data" button. “The identification number is not in
the right format. Please verify the
identification number.”
2. Front office clerk submit the Front Office Clerk submit citizen NUIS and IFO system display a message type:
wrong NUIS. clicks the "get data" button. “No data found for this
Page 7
 UAT-User Acceptance testing

identification number”.

Testing summary and Signatures

Time of start Time of finish

Results: Successful, without problems

Successful, with notes
Not successful:

Choose problem priority with biggest priority:  P1  P2  P3

Additional tests will be done on: Time:

Notes and suggestions:

Company Institution Institution

Tester Inspector Inspector

Signature: Signature: Signature:

TC-GG05 - Integrate with HRMIS system

PRIMARY ACTOR

Page 8
 UAT-User Acceptance testing

Front Office Clerk

PRECONDITIONS SUCCESS GUARANTEES

Front Office Clerk is successfully logged in the system with its own The system is successfully integrated with HRMIS system.
credentials.
GG, IFO system DIS, HRMIS DIS is up and running.
IFO system account in GG has permissions to consume personal data
service.

Integrate with HRMIS system

Integrate with HRMIS system Test Scenario Procedure/Inputs Expected Results Pass/Fail
1. Front Office Clerk creates a new Front Office Clerk clicks the “create new The system is integrated with
complaint and select the institution. complaint” button and selects the HRMIS system and display the list of
institution. all institutions registered in HRMIS.

Testing summary and Signatures

Time of start Time of finish

Results: Successful, without problems

Successful, with notes
Not successful:

Choose problem priority with biggest priority:  P1  P2  P3

Additional tests will be done on: Time:

Notes and suggestions:

Page 9
 UAT-User Acceptance testing

Company Institution Institution

Tester Inspector Inspector

Signature: Signature: Signature:

Page 10