0
|
1 |
//
|
|
2 |
// Copyright (c) 2005-2009 Nokia Corporation and/or its subsidiary(-ies).
|
|
3 |
// All rights reserved.
|
|
4 |
// This component and the accompanying materials are made available
|
|
5 |
// under the terms of "Eclipse Public License v1.0"
|
|
6 |
// which accompanies this distribution, and is available
|
|
7 |
// at the URL "http://www.eclipse.org/legal/epl-v10.html".
|
|
8 |
//
|
|
9 |
// Initial Contributors:
|
|
10 |
// Nokia Corporation - initial contribution.
|
|
11 |
//
|
|
12 |
// Contributors:
|
|
13 |
//
|
|
14 |
// Description:
|
|
15 |
//
|
|
16 |
|
|
17 |
LOAD_SERVER te_RegBlockTestSuite
|
|
18 |
|
|
19 |
START_TESTCASE DT-TEF-TestBlock-0112
|
|
20 |
//! @SYMTestCaseID DT-TEF-TestBlock-0112
|
|
21 |
//! @SYMCreationDate 10-11-2008
|
|
22 |
//! @SYMAuthor extshuohuang
|
|
23 |
//! @SYMTestPriority High
|
|
24 |
//! @SYMTestCaseDesc This case from defect DPDEF129608. when panic or leave happened with number -16(KErrServerBusy), testexecute will retry again.
|
|
25 |
//! two scenario:
|
|
26 |
//! 1. In some situation, test server really busy, testexecute should retry.
|
|
27 |
//! 2. On other wise, test server execute some test, this test require a server which busy. test server should notice the server busy and retry.
|
|
28 |
//!
|
|
29 |
//! So this test case only test server leave(panic) with -16.this not a really test server busy..So the test should go on next test without retry current.
|
|
30 |
//! Both shareddata and non-shareddata should act same.
|
|
31 |
//! @SYMTestExpectedResults test block pass, panic happens with -16
|
|
32 |
//! @SYMTestActions 1.read ini test number;
|
|
33 |
//! 2.panic with the number.
|
|
34 |
START_TEST_BLOCK 100 te_RegBlockTestSuite ${SYSDRIVE}\TestData\configs\te_RegBlockTestSuite.ini
|
|
35 |
CREATE_OBJECT te_RegBlockTestWrapper serverbusy_panic-016
|
|
36 |
COMMAND serverbusy_panic-016 PanickingFunction serverbusy_panic-016_obj_Panic
|
|
37 |
END_TEST_BLOCK !PanicCode=-16
|
|
38 |
END_TESTCASE DT-TEF-TestBlock-0112
|