Symbian3/PDK/Source/GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C.dita
changeset 1 25a17d01db0c
child 3 46218c8b8afa
equal deleted inserted replaced
0:89d6a7a84779 1:25a17d01db0c
       
     1 <?xml version="1.0" encoding="utf-8"?>
       
     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
       
     3 <!-- This component and the accompanying materials are made available under the terms of the License 
       
     4 "Eclipse Public License v1.0" which accompanies this distribution, 
       
     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
       
     6 <!-- Initial Contributors:
       
     7     Nokia Corporation - initial contribution.
       
     8 Contributors: 
       
     9 -->
       
    10 <!DOCTYPE reference
       
    11   PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
       
    12 <reference id="GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C" xml:lang="en"><title>SysLibs
       
    13 Test Suite Details</title><prolog><metadata><keywords/></metadata></prolog><refbody>
       
    14 <section> <title>Test Script Source Tree Location</title>      <p>Descriptions
       
    15 of the test cases in this test suite can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\scripts\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
       
    16 <section><title>Test Script EPOC tree Location</title> <p>When the tests are
       
    17 built for emulator or hardware (winscw or armv5), the script is exported into
       
    18 the following location in the epoc tree. </p> <p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
       
    19 <section><title>Test Script Build Location</title> <p>When the tests are built,
       
    20 the scripts are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\release\&lt;winscw|armv5&gt;\&lt;udeb|urel&gt;\Z\ecom</filepath> </p> <p> <b>Note:</b> When the tests are built to be executed on hardware the
       
    21 files are built into the z: drive of the ROM. </p> </section>
       
    22 <section><title>Test Data Source Tree Location</title> <p>The test suite contains
       
    23 following test data files: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\testdata\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> <p>The
       
    24 global environment file located at: </p> <p> <filepath>...\syslibsapitest\syslibssvs\testdata\&lt;platform&gt;\t_syslibs.ini</filepath> </p> </section>
       
    25 <section><title>Test Data Files EPOC Tree Location</title> <p>When the tests
       
    26 are built for emulator or hardware (winscw/armv5), the data files are exported
       
    27 into the following location in the epoc tree. </p> <ul>
       
    28 <li id="GUID-59493D8D-9350-5EBA-A7CC-D4276340CBC3"><p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> </li>
       
    29 <li id="GUID-62EAD10E-A155-50F3-965C-C36242479C9C"><p> <filepath>%EPOCROOT%\epoc32\data\Z\syslibs\t_syslibs.ini</filepath>  </p> </li>
       
    30 </ul> </section>
       
    31 <section><title>Test Data Files Emulator Location</title> <p>When the tests
       
    32 are built, the test data files are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\
       
    33                 release\winscw\&lt;udeb/urel&gt;\Z\ecom\.</filepath>  </p> <p> <b>Note:</b> When
       
    34 the tests are built to be executed on hardware the files are built into the
       
    35 z: drive of the ROM </p> </section>
       
    36 <section><title>Test .driver File</title> <p>The <filepath>syslibs.driver</filepath> file
       
    37 found in </p> <p> <filepath>…\syslibsapitest\syslibssvs\testsuites\syslibs\</filepath>  </p> <p>is
       
    38 used by the test driver to construct the test suite tree structure and export
       
    39 all the appropriate files to the correct location in the epoc32 tree and on
       
    40 the device. </p> <p>When the tests are built, the <filepath>.driver</filepath> file
       
    41 can be found in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\testdriver\testproduct</filepath>  </p> </section>
       
    42 <section><title>TCS file source location</title> <p>The <filepath>.tcs</filepath> file
       
    43 can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\config\t_syslibs.tcs</filepath>  </p> </section>
       
    44 <section><title>TCS file build location</title><p>When the tests are built,
       
    45 the <filepath>.tcs</filepath> file is generated into the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\&lt;winscw|armv5&gt;\&lt;udeb|urel&gt;\Z\ecom</filepath> </p>      </section>
       
    46 </refbody></reference>