//

// Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).

// All rights reserved.

// This component and the accompanying materials are made available

// under the terms of the License "Eclipse Public License v1.0"

// which accompanies this distribution, and is available

// at the URL "http://www.eclipse.org/legal/epl-v10.html".

//

// Initial Contributors:

// Nokia Corporation - initial contribution.

//

// Contributors:

//

// Description: 

//

//

// Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).

// All rights reserved.

// This component and the accompanying materials are made available

// under the terms of the License "Symbian Foundation License v1.0"

// which accompanies this distribution, and is available

// at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".

//

// Initial Contributors:

// Nokia Corporation - initial contribution.

//

// Contributors:

//

// Description:

//

//tups_install

//PRINT Run Basic test cases PREQ1262 for integration test

//

//  Prepare various clones of TUPSInteg.exe with different SIDs.

//  Don't forget to delete clones at the end of test script.

//  but do not delete original one !!!!

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 80001234 TUPSInteg_2.exe

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 80002222 TUPSInteg_3.exe  

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 10004444 TUPSInteg_4.exe 

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 810  	-SID 10006666 TUPSInteg_allfiles_readdevice.exe

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 10 	-SID 10007777 TUPSInteg_readdevice.exe

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 20 	-SID 10008888 TUPSInteg_writedevice.exe

RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1cf00 -SID 101F7790 TUPSInteg_minor.exe 

// load suites

LOAD_SUITE TUPSInteg_1

LOAD_SUITE TUPSInteg_unprotected

// load clones

LOAD_SUITE TUPSInteg_2

LOAD_SUITE TUPSInteg_3

LOAD_SUITE TUPSInteg_4

LOAD_SUITE TUPSInteg_allfiles_readdevice

LOAD_SUITE TUPSInteg_readdevice

LOAD_SUITE TUPSInteg_writedevice

LOAD_SUITE TUPSInteg_minor

// Load software step installer.

LOAD_SUITE tups_install

LOAD_SUITE tups_backuprestore

//! @SYMTestCaseID SEC-UPS-MISC-0001

//! @SYMTestCaseDesc Set up properties for policy evaluators and dialog creators, and Delete Existing Database

START_TESTCASE SEC-UPS-MISC-0001

RUN_TEST_STEP 100 TUPSInteg_1 PropertyStep z:\tups\integ\scripts\tups_properties.ini PropertiesToDestroy

// Set up properties for policy evaluators and dialog creators.

RUN_TEST_STEP 100 TUPSInteg_1 PropertyStep z:\tups\integ\scripts\tups_properties.ini PropertiesToCreate

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

END_TESTCASE SEC-UPS-MISC-0001

//********************** SEC-UPS-A : BASIC USER PROMPTING  **********************

//! @SYMTestCaseID SEC-UPS-INTEG-A001

//! @SYMTestCaseDesc User prompt service: option “only this session”

//!                  (only_this_session)

//!		

//! @SYMPREQ PREQ1262

//! @SYMREQ REQ7367, REQ7410, REQ7411, REQ7412, REQ7413, REQ7414, REQ7415, REQ7417, REQ7446

//! @SYMTestPriority Critical

//! @SYMTestStatus   Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog that matches the UID of the service 	

//!			offered by the “system server”.

//!

//!			

//!			Test Actions:

//!			• Launch “test client” which tries to connect to a system server and use service.

//!			• System server asks for a user prompt to the UPS.

//!			• When UPS prompts user, select the “Only this session” option.

//!			• Check that now the “test client” can use the intended service from the “system server”.

//!			• Check again In same session that client still can use test service without need of user prompt. 

//!			• Disconnect session and create new one.

//!			• Ask “test client” to request again for the same service to the system server.  This should cause 	

//!			the service provided to request for a new user prompt.

//!			• Select again “Only this session” option.

//!			• Check that “test client” can use again the intended service from system server.

//!

//! @SYMTestExpectedResults 	• User prompt service dialog is displayed correctly in both occasions that “test client” 

//!				request for authorisation.

//!				• Information displayed about the client is complete (see Appendix A).

//!				• “Test client” can use service from system server in both  occasions after selecting “Only 	

//!				this session”

//!				• Information about the “Test client” is displayed correctly by user prompt.

//!				• Decision DB is not affected by previous operation as “only this session” is not expected to 

//!				be stored. 

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-A001

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini only_this_session

END_TESTCASE SEC-UPS-INTEG-A001

//! @SYMTestCaseID SEC-UPS-INTEG-A002

//! @SYMTestCaseDesc User prompt service: User prompt service: option “never”

//!                  (never)

//!		

//! @SYMPREQ PREQ1262

//! @SYMREQ REQ7367, REQ7372, REQ7374

//!

//! @SYMTestPriority Critical

//! @SYMTestStatus   Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the 	

//!			service offered by the “system server”.

//!			

//!			Test Actions:

//!			• Launch “test client” which tries to connect to a system server and use service.

//!			• System server asks for a user prompt to the UPS.

//!			• When UPS prompts user, select the “Never” option.

//!			• Check that now the “test client” can NOT use the intended service after user selected “never”.

//!			• Disconnect session and create new one.

//!			• Ask “test client” to request again for the same service to the system server.  System server should 

//!			deny access to “test client” immediately without showing user prompt. Make sure that UPS was invoked 	

//!			again.

//!

//!

//! @SYMTestExpectedResults 	• User prompt service dialog is displayed correctly.

//!				• Security dialog is displayed within one second (1 sec) of client request for service. 

//!				• Information displayed about the client is complete (see Appendix A).

//!				• “Test client” can NOT use service from system server after selecting “Never”

//!				• Decision DB is updated correctly with the never decision. 

//!				• The second time the “Test client” tries to access the service from the system server it 	

//!				should receive a silent denial. 

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-A002

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini never

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini never_b

END_TESTCASE SEC-UPS-INTEG-A002

//! @SYMTestCaseID SEC-UPS-INTEG-A003

//! @SYMTestCaseDesc User prompt service: option “Always”

//!                  (always)

//!		

//! @SYMPREQ PREQ1262

//! @SYMREQ REQ7428, REQ7429, REQ7367, REQ7372, REQ7374, REQ7493

//!

//! @SYMTestPriority Critical

//! @SYMTestStatus   Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the 	

//!			service offered by the “system server”.

//!			• Special: make sure that client have all necessary capabilities in order to test  REQ7493

//!			

//!			Test Actions:

//!			• Launch “test client” which tries to connect to a system server and use service.

//!			• System server asks for a user prompt to the UPS.

//!			• When UPS prompts user, select the “Always” option.

//!			• Check in same session that now the “test client” now can use the intended service after user 		

//!			selected “Always”.

//!			• Ask “test client” to request again for the same service to the system server.  System server should 

//!			give immediate access to “test client” without showing user prompt (in same session).  

//!			• Disconnect session and create new one.

//!			• Ask “test client” to request again for the same service to the system server.  System server should 

//!			give immediate access to “test client” without showing user prompt.  Make sure that UPS was invoked 	

//!			again.

//!

//! @SYMTestExpectedResults 	• User prompt service dialog is displayed correctly.

//!				• Security dialog is displayed within one second (1 sec) of client request for service. 

//!				• Information displayed about the client is complete (see Appendix A).

//!				• “Test client” can use service from system server after selecting “Always”

//!				• Decision DB is updated correctly with the Always decision. 

//!				• The second time the “Test client” tries to access the service from the system server it 	

//!				should receive immediate access.  

//!				• The response time from UPS for second use of test client is 100 ms (H4 board without demand 

//!				paging) 

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-A003

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini always

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini always_b

END_TESTCASE SEC-UPS-INTEG-A003

//! @SYMTestCaseID SEC-UPS-INTEG-A004

//! @SYMTestCaseDesc User prompt service: “Yes” or “No” selection”

//!                  (yes_or_no)

//!		

//! @SYMPREQ PREQ1262

//! @SYMREQ REQ7372

//!

//! @SYMTestPriority Critical

//! @SYMTestStatus   Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the 	

//!			service offered by the “system server”.

//!			• Policy is set to display “yes” or “no” option

//!			

//!			Test Actions:

//!			• Launch “test client” which tries to connect to a system server and use service.

//!			• System server asks for a user prompt to the UPS.

//!			• When UPS prompts user, select the “yes” option.

//!			• Check that now the “test client” now can use the intended service.

//!			• In same session that before, request uses service.

//!			• UPS should prompt user again. Select yes  

//!			• Launch “test client” in a new session. When security dialog is displayed select “no”.

//!			• Check that test client can not access intended service. 

//!

//! @SYMTestExpectedResults 	• User prompt service dialog is displayed correctly.

//!				• Security dialog is displayed within one second (1 sec) of client request for service. 

//!				• Information displayed about the client is complete (see Appendix A).

//!				• Decision DB does not store any new decision. 

//!				• Access to test service is denied or granted accordingly.

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-A004

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini yes_or_no

END_TESTCASE SEC-UPS-INTEG-A004

//********************** SEC-UPS-B : USE CASES FOR UPS INVOLVING CONCURRENCY  **********************

//! @SYMTestCaseID 	SEC-UPS-INTEG-B004

//! @SYMTestCaseDesc 	Concurrent process can access service despite unattended security dialog.

//!                     (Unattended_Dialog)

//!		

//! @SYMPREQ 		PREQ1262

//! @SYMREQ  		REQ7427

//!

//! @SYMTestPriority 	Critical

//! @SYMTestStatus   	Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the 

//!			service offered by the “system server”.

//!

//!			Test Actions:

//!			• Launch 3 “test client” (A, B & C) which requests use of different system servers. Client A should

//!			not have any decision related to it stored in DB, Clients B should have a decision “Always” stored 

//!			in DB, Client C should have decision “Never” stored in DB. Make sure that Client B & C are launch 

//!			after security dialog is displayed for Client A. 

//!			• Do not act in the security dialog for Client A when this one is displayed.

//!			• Check that Client B can access intended test service.

//!			• Check that Client C can not access intended test service and did receive a denial response.

//!			• Act now in security dialog for Client A, select “always”.

//!			• Check that Client A can access intended test service.

//!

//! @SYMTestExpectedResults 	• Final check in Decision DB shows 3 decisions stored: “Always” for Clients A & B,  “Never” 

//!				for Client C.

//!				• Accesses to service were granted for Clients A & B.

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-B004

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

// Setup up the Database so that Client B has an 'Always' Decision and Client C has a 'Never' Decision stored

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientB_Setup

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientC_Setup

// Run 3 concurrent clients with a Coordinator to ensure that the Clients are synchronised

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_Coordinator

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientA

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientB

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientC

CONSECUTIVE

// Database Management Checks

RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_dbManagementcheck

END_TESTCASE SEC-UPS-INTEG-B004

//! @SYMTestCaseID 	SEC-UPS-INTEG-B005

//! @SYMTestCaseDesc 	Cancellation of UPS request in concurrent system server.

//!                     (concurrent_cancellation)

//!		

//! @SYMPREQ 		PREQ1262

//! @SYMREQ  		REQ7427, REQ7431, REQ7432

//!

//! @SYMTestPriority 	Critical

//! @SYMTestStatus   	Implemented

//! @SYMTestActions 	Preconditions:

//!			• There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the 

//!			service offered by the “system server”.

//!

//!			Test Actions:

//!			• Launch 2 “test client” (A & B ) which requests use of different system servers. Client A 		

//!			should have a decision “Always” stored in DB, client B should have decision “Never” stored in DB. 	

//!			Client A & B run continuously and they request periodic use of a test service, each of this request 	

//!			should cause UPS to be invoked, UPS should continuously issue an appropriate silence response for A & 

//!			B. 

//!			• Launch “test client C” which requests use of different system servers. This client C does not have 	

//!			any related decision stored in DB.

//!			• The system server for client C is expected to request UPS for security dialog.

//!			• Do not act in security dialog displayed for client C, instead instruct system server for client C 	

//!			to cancel previous request made to UPS.

//!			• Make sure that clients A & B can still receive appropriate silent response from UPS despite 		

//!			cancellation of request by system server attending client C.

//!			• Launch test client D which should attempt use of same service attempted by client C. Security 	

//!			dialog should be displayed, select “Always”.

//!			• Check that client D can access intended service.

//!			• Launch client D in new session and check that it received silent acceptance.

//!

//!

//! @SYMTestExpectedResults 	• Final check in Decision DB shows 2 decisions stored: “Always” for Clients A,  “Never” for 	

//!				Client B.

//!				• Access to service was granted for Clients A & D.

//!				• Access to service was denied for Clients B.	

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-B005

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA_setup

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB_setup

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientC_cancel

RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientD

CONSECUTIVE

// Concurrent cancellation with UPS calling the same server, policy evaluator, dialog creator and policy from clients B + D

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB_samepolicy

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientC_cancel

RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientD_samepolicy

CONSECUTIVE

END_TESTCASE SEC-UPS-INTEG-B005

//! @SYMTestCaseID 	SEC-UPS-INTEG-B008

//! @SYMTestCaseDesc 	Early closure of client with concurrent processes, policy evaluator stage

//!                     (client_dying_at_evaluator_point)

//!		

//! @SYMPREQ 		PREQ1262

//! @SYMREQ  		REQ7427 

//!

//! @SYMTestPriority 	Critical

//! @SYMTestStatus   	Implemented

//! @SYMTestActions 	Preconditions:

//!			•  There is an appropriate policy, policy evaluator and dialog creator that 

//!			   matches the UID of the service offered by the “system server”.

//!

//!			Test Actions:

//!			•  Launch 2 “test client” (A & B) which requests use of different system servers.

//!			   Client A should have a decision “Always” stored in DB, client B should have 

//!		           decision “Never” stored in DB. Clients A & B run continuously and they request

//!			   periodic use of a test service, each of this request should cause UPS to be 

//!			   invoked, UPS should continuously issue an appropriate silence response for A & B. 

//!			•  Launch “test client C” which requests use of a different system server. System 

//!			   server will invoke UPS and this one should invoke a policy evaluator. When 

//!			   policy evaluator is running shut down test client C.

//!			•  Make sure that Clients A & B can still receive appropriate silent response from UPS.

//!

//! @SYMTestExpectedResults 

//!			•  Final check in Decision DB shows 2 decisions stored: “Always” for Clients A, “Never”

//!			   for Client B.

//!			•  Access to service was granted for Clients A. 

//!			•  Access to service was denied for Clients B & C. 

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-INTEG-B008

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00a

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00b

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini dying_client_at_evaluator_Coordinator

RUN_TEST_STEP 100 TUPSInteg_minor DyingClient z:\tups\integ\scripts\tups_integ.ini dying_client_at_evaluator

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00a

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00b

CONSECUTIVE

// Database Management Checks

RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini client_dying_at_evaluator_point_dbManagementCheck

END_TESTCASE SEC-UPS-INTEG-B008

//! @SYMTestCaseID 	SEC-UPS-B009

//! @SYMTestCaseDesc 	Early closure of client with concurrent processes, dialog displayed stage

//!                     (client_dying_at_dialog_point)

//!		

//! @SYMPREQ 		PREQ1262

//! @SYMREQ  		REQ7427 

//!

//! @SYMTestPriority 	Critical

//! @SYMTestStatus   	Implemented

//! @SYMTestActions 	Preconditions:

//!			•  There is an appropriate policy, policy evaluator and dialog creator that 

//!			   matches the UID of the service offered by the “system server”.

//!			Test Actions:

//!			•  Launch 2 “test client” (A & B) which requests use of different system 

//!			   servers. Client A should have a decision “Always” stored in DB, client B 

//!			   should have decision “Never” stored in DB. Clients A & B run continuously and 

//!			   they request periodic use of a test service, each of this request should cause 

//!	                   UPS to be invoked, UPS should continuously issue an appropriate silence response 

//!			   for A & B. 

//!			•  Launch “test client C” which requests use of a different system server. System 

//!			   server will invoke UPS and at some stage a security dialog will be invoked. When 

//!			   security dialog is displayed do not act on this one and shut down test client C.

//!			•  Make sure that Clients A & B can still receive appropriate silent response from UPS.

//!

//! @SYMTestExpectedResults 

//!			•  Final check in Decision DB shows 2 decisions stored: “Always” for Clients A,  

//!			   “Never” for Client B.

//!			•  Access to service was granted for Clients A. 

//!		        •  Access to service was denied for Clients B & C. 

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-B009

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00a

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00b

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini dying_client_at_dialog_Coordinator

RUN_TEST_STEP 100 TUPSInteg_minor DyingClient z:\tups\integ\scripts\tups_integ.ini dying_client_at_dialog

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00a

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00b

CONSECUTIVE

// Database Management Checks

RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini client_dying_at_dialog_point_dbManagementCheck

END_TESTCASE SEC-UPS-B009

//! @SYMTestCaseID 	SEC-UPS-B010

//! @SYMTestCaseDesc 	Multiple clients requesting multiple services in concurrent manner.

//!                     (multiple_client_requests_concurrent)

//!		

//! @SYMPREQ 		PREQ1262

//! @SYMREQ  		REQ7427 

//!

//! @SYMTestPriority 	Critical

//! @SYMTestStatus   	Implemented

//! @SYMTestActions 	Preconditions:

//!			• As set in test assumptions section on detail description of this test.

//!

//!			Test Actions:

//!			• Execute test actions as set in “tests sequence part 1” above.

//!			• Execute test actions as set in “tests sequence part 2” above.

//!			• Reset test clients and test system servers.

//!			• Execute test actions as set in “tests sequence part 3” above.

//!

//! @SYMTestExpectedResults 	Test services are granted/denied accordingly as set in detail test description.

//!

//! @SYMTestType CIT

START_TESTCASE SEC-UPS-B010

// Delete Existing Database

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

RUN_UTILS DeleteFile c:\private\10283558\database\ups.db

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client1

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client2

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client3

RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client4

CONSECUTIVE

CONCURRENT

RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client1

RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client2

RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client3

RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client4

CONSECUTIVE

// Close and Reset UPS

RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps

CONCURRENT