|
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 concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-3C26B5B2-1B90-5F96-9342-1D53F6EDD94F" xml:lang="en"><title>F32 Test |
|
13 Technology Description</title><shortdesc>Describes the high level test philosophy, scope and the types of |
|
14 test used in F32 technology.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
15 <p>This topic provides a high level information about the Base test technology |
|
16 area. It also provides an overview of the test technology area, its coverage, |
|
17 test environment setup and how to find further information about the test |
|
18 suites offered by this test technology area. </p> |
|
19 <p>The aim is to provide and deliver a product quality set of test suites |
|
20 that can be used internally within Symbian and by external groups who have |
|
21 access to the Symbian test source code. </p> |
|
22 <section id="GUID-2268DFDE-1204-441A-823B-6E2855B45658"><title> Scope</title> <p><b> Components under test</b> </p> <p>The Base subsystem is the lowest layer |
|
23 in the Symbian platform software stack. It contains the core components, such |
|
24 as the kernel, user library, file server, and device drivers, for every supported |
|
25 hardware platform. </p> <p>This suite tests the F32_EKA2 (file server) and |
|
26 FAT32 components. </p> <p><b>Test |
|
27 types</b> </p> <p>The suite has three sub-suites: validation, performance |
|
28 and conformance. </p> <p><b>Validation |
|
29 test suite</b> </p> <p>The <xref href="GUID-E1EBD343-C8A6-51E5-B158-9A1D0328D3B3.dita">Validation |
|
30 Test Suite</xref> provides a series of tests to verify that published APIs |
|
31 perform as described in the Symbian platform library. The tests are intended |
|
32 for regression and compatibility verification. </p> <p>The validation suite |
|
33 uses Dual Driver tests to test the dual driver feature on the phone. DUAL |
|
34 Drive tests are configured to run on two drives of the same type having common |
|
35 interface. </p> <p><b>Performance |
|
36 Test Suite</b> </p> <p>The <xref href="GUID-CDD23CE8-15F7-557B-9C58-ECEE9E13528A.dita">Performance |
|
37 Test Suite</xref> is intended for assessing and benchmarking file server performance. </p> <p><b>Conformance Test Suite</b> </p> <p>The <xref href="GUID-FFDD3689-A83B-5E67-A2BD-7723B141E198.dita"> FAT32 |
|
38 Conformance Test Suite</xref> ensures the file server's compliance with FAT32. </p> </section> |
|
39 <section id="GUID-2793C842-EBA9-443B-82E6-CB48A74BAD5C"><title> Test Environment</title> <p><b> Device Setup</b> </p> <p>The device under test (a hardware platform, |
|
40 a phone or an emulator) must contain an appropriate Symbian platform build |
|
41 or licensee UI build. </p> <p><b>PC |
|
42 Setup</b> </p> <p>The PC must have a Symbian Developer Kit (or licensee equivalent), |
|
43 an PDT and appropriate compilers to build the test code (for example Code |
|
44 Warrior, RVCT or GCCE). </p> <p><b>Test |
|
45 Dependencies</b> </p> <p>The base test suite has no dependencies other than |
|
46 those common to all test suites. </p> <p><note> Any mention of “epoc32” is |
|
47 offset by %EPOCROOT%, the full path where the epoc tree is installed. </note></p> <p id="GUID-60931C28-3CCB-5396-A815-641A6D1A0E9B"><b> Building and Execution</b> </p> <p> For |
|
48 general information about test suite structure refer to <b>Symbian Verification |
|
49 Suite » TestDriver</b>. </p> <p>The following illustrates the F32 test suite |
|
50 structure: </p> <codeblock id="GUID-89572E92-2B12-5ACC-B9B3-CE908565AD90" xml:space="preserve"><Component> - base |
|
51 <Validation suite> - validation |
|
52 <Sub-component> - f32 |
|
53 <Manual tests> - f32-manual |
|
54 <RAM-drive specific tests> - ram-manual |
|
55 <Suite> - pbase-f32-sfsrv-publicapi-rem-manual-suite |
|
56 <Dual Drive Tests>- f32-dualdrive> |
|
57 <Suite> - pbase-f32-sfsrv-Publicapi-ram-DualDrive-suite |
|
58 <Automated tests> - f32-automated |
|
59 <Suite> - pbase-f32-sfsrv-publicapi-any-suite |
|
60 <System drive specific tests> - os |
|
61 <Suite> - pbase-f32-sfsrv-publicapi-os-suite |
|
62 <ROM-drive specific tests> - rom |
|
63 <Suite> - pbase-f32-publicapi-sfsrv-rom-suite |
|
64 <NAND-drive specific tests> - nand |
|
65 <Suite> - pbase-f32-sfsrv-publicapi-nand-suite |
|
66 <RAM-drive specific tests> - ram |
|
67 <Non-removable RAM-drive specific tests> - fixed |
|
68 <Suite> - pbase-f32-publicapi-sfsrv-ram-suite |
|
69 <Suite> - pbase-f32-publicapi-sfsrv-rem-suite |
|
70 <Performance suite> - performance |
|
71 <Sub-component> - f32 |
|
72 <Scenario variant> - small |
|
73 <Suite> - pbase-f32-rfile-performance-small |
|
74 <Suite> - pbase-f32-rfs-performance-small |
|
75 <Scenario variant> - medium |
|
76 <Suite> - pbase-f32-rfile-performance-medium |
|
77 <Suite> - pbase-f32-rfs-performance-medium |
|
78 <Scenario variant> - large |
|
79 <Suite> - pbase-f32-rfile-performance-large |
|
80 <Suite> - pbase-f32-rfs-performance-large |
|
81 <Conformance suite> - conformance |
|
82 <Sub-component> - f32 |
|
83 <Sub-component> - FAT32 |
|
84 <Suite> - f32-fat32-conformance</codeblock> <p>This structure can |
|
85 be seen in the following location after building the test suite: <filepath>%EPOCROOT%\epoc32\testdriver\testproduct</filepath>. </p> <p>The |
|
86 hierarchical test suite structure facilitates easy build and execution of |
|
87 the complete test suite or part of it. For example, if the path specified |
|
88 is: </p> <ul> |
|
89 <li id="GUID-24E673FF-86FC-5029-94D4-5F7618D1AFC3"><p> <filepath> base</filepath>: |
|
90 The entire suite is built/run. </p> </li> |
|
91 <li id="GUID-AFD445CF-5FC5-5E6E-8E03-984CF9F269A0"><p> <filepath> base.validation.f32</filepath>: |
|
92 All the suites F32 are built/run. </p> </li> |
|
93 <li id="GUID-09B4561B-79DB-5BD4-B3D3-FD2E332F332E"><p> <filepath> base.validation.f32.f32-automated</filepath>: |
|
94 Only F32 automated test is built/run. </p> </li> |
|
95 <li id="GUID-A947006E-224B-5034-8A6A-F3242BD28A70"><p> <filepath> base.validation.f32.f32-manual</filepath>: |
|
96 Only F32 manual test is built/run. </p> </li> |
|
97 <li id="GUID-08256C88-4E66-57D1-A68D-A7F6AFBC30D5"><p> <filepath> base.validation.f32.f32-dualdrive</filepath>: |
|
98 Only f32 dual drive tests is built/run. </p> </li> |
|
99 <li id="GUID-878D50ED-547C-5741-AE61-A61A763F8A40"><p> <filepath> base.validation.f32.f32-automated.ram</filepath>: |
|
100 Only tests on RAM are built/run. </p> </li> |
|
101 <li id="GUID-FF860F6A-6436-5AD9-81D0-8A7F3EF73417"><p> <filepath>base.validation.f32.f32-automated.ram.fixed</filepath>: |
|
102 Only tests on non-removable RAM are built/run. </p> </li> |
|
103 <li id="GUID-0ABED61A-1B55-53BA-AEE9-9A195DAA6A31"><p> <filepath> base.validation.f32.f32-automated.rom</filepath>: |
|
104 Only tests on ROM are built/run. </p> </li> |
|
105 <li id="GUID-961D3BA3-245F-56BA-A325-F3568E86BA87"><p> <filepath> base.validation.f32.f32-automated.os</filepath>: |
|
106 Only OS suite is built/run. </p> </li> |
|
107 <li id="GUID-20137842-292D-5A23-A630-5CB82672A927"><p> <filepath>base.validation.f32.f32-automated.ram.fixed</filepath>: |
|
108 Only tests on non-removable RAM are built/run. </p> </li> |
|
109 </ul> <p><b> General |
|
110 environment setup</b> </p> <ol id="GUID-09208F08-2F83-5758-9CD7-842834C6CD41"> |
|
111 <li id="GUID-3014B1D5-6A0C-57DE-9B9C-F4CE43CC4DE7"><p>Refer to specific sub-component |
|
112 test suite description in <xref href="GUID-8D89BC22-3008-5A43-8BBC-C8F2985D71C1.dita">Base |
|
113 Verification Suite</xref> for details about configuration and building additional |
|
114 components before building the test suite. </p> </li> |
|
115 <li id="GUID-5BE45723-65AC-5C1A-BF03-29A2391C5793"><p>The entire Base Test |
|
116 product can be built from <filepath>...\baseapitest\basesvs\group\</filepath>. </p> </li> |
|
117 <li id="GUID-3D442168-3547-5120-9700-995B21E83F2D"><p>Individual test components |
|
118 can be built from the respective group directories. For example, <filepath>...\baseapitest\basesvs\validation\f32\group\</filepath>. </p> <p> </p> <p><userinput>bldmake bldfiles</userinput> </p> <p><userinput>abld test |
|
119 build <WINSCW/ARMV5> <udeb/urel></userinput> </p> </li> |
|
120 </ol> <p><b> Steps |
|
121 to build and execute tests using TestDriver</b> </p> <p>Communication between |
|
122 the PC and the device under test (Symbian platform device) is enabled using |
|
123 STAT. So, the device under test must have STAT installed. </p> <p/> <p><b>For WINSCW platform: </b> </p> <ol id="GUID-60208068-3B9B-5D81-B708-D20AD21D1857"> |
|
124 <li id="GUID-2A38FFA5-DABB-5C68-8CC1-CD43AFBAE16F"><p> <b>Configure TestDriver |
|
125 using the following script:</b> </p> <p> <filepath>...\baseapitest\basesvs\group\testdriversetup.bat</filepath> </p> </li> |
|
126 <li id="GUID-6DE34C54-C769-5AC8-BDBE-F32AFAC60E04"><p> <b>Build the test code: </b> </p> <p><userinput>testdriver |
|
127 build –p <winscw/armv5> –b <urel/udeb> –s base[.<specific test suite |
|
128 path>]</userinput> </p> <p>Testdriver commands can be run from any location. </p> </li> |
|
129 <li id="GUID-74DAF846-94E3-5C7A-B853-38B26B85F41C"><p> <b>To execute the Tests |
|
130 : </b> </p> <p><userinput>testdriver run</userinput> </p> </li> |
|
131 </ol> <p><b>For ARMV5 platform: </b> </p> <p> <b>Communication between PC and hardware:</b> </p> <p>The |
|
132 hardware reference board (for example H4) must be connected to the PC through |
|
133 USB or serial cable. The ROM image is built on the PC and transferred to the |
|
134 hardware board through MMC card. </p> <ol id="GUID-F7A7A995-AEDF-52AB-942C-FCC8063679D5"> |
|
135 <li id="GUID-D6B62BB6-9563-57E0-BB51-9CE0F2411B5C"><p> <b> Configure TestDriver |
|
136 using the following script: </b> </p> <p> <filepath>...\baseapitest\basesvs\group\testdriversetup.bat</filepath> </p> </li> |
|
137 <li id="GUID-D0EAD784-5BB2-5394-9F75-A0F5AA193E01"><p> <b> Build the test |
|
138 code:</b> </p> <p><userinput>testdriver build –p <winscw/armv5> –b <urel/udeb> |
|
139 –s base[.<specific test suite path>]</userinput> </p> <p>Testdriver commands |
|
140 can be run from any location. </p> </li> |
|
141 <li id="GUID-B205290E-37F4-566F-8987-4A9D7387996B"><p> <b> Build the ROM image:</b> </p> <p><userinput>buildrom |
|
142 -D_STARTUPMODE2 -D_EABI=ARMV5 -DRVCT -DUSE_STRONG_CRYPTOGRAPHY <h2/h4hrp> |
|
143 techview_statapi td_base</userinput> </p> <p> <b>Note</b> The ROM building |
|
144 commands are different for NAND images and enabling Dual Drive. </p> </li> |
|
145 <li id="GUID-8B53FA6B-C8E0-5FDE-AF72-4EA5EA45F056"><p>Transfer the ROM to |
|
146 the device and start-up. </p> </li> |
|
147 <li id="GUID-4E897DE9-F2A9-51D9-80C9-8ACA5F6C1852"><p> <b>Execute the Tests: </b> </p> <p><userinput>testdriver |
|
148 run -t <transport service> </userinput> </p> <p>Transport service may be |
|
149 “serial<COM port number that is connected to the board>”, “bt<COM port |
|
150 number for BT dongle>” or “usb<mapped port number>” </p> </li> |
|
151 </ol> <p> <note> All scripts and test data are automatically removed from |
|
152 the system drive of the device under test after the execution. </note></p> <p id="GUID-123789D7-482A-560A-ADAA-E2D972BB4918"><b>Steps to build and execute |
|
153 tests manually (Tests built into ROM)</b> </p> <p><b>For WINSCW platform: </b> </p> <ol id="GUID-905EA8B7-1EDC-59F6-A43B-D9C3488E68E5"> |
|
154 <li id="GUID-0FB2AB82-88C3-58E7-A0DA-1A1A02A7ECD8"><p> <b>Select your Setup |
|
155 Script: </b> </p> <p>For example <filepath>setup-PBASE-F32-Sfsrv-PublicApi.script</filepath> is |
|
156 used to run only the F32_EKA2 validation test suite. </p> </li> |
|
157 <li id="GUID-0C3B70D2-0805-52E7-B11D-6FB7AF516A33"><p> <b>Change directory |
|
158 to: </b> </p> <p> <filepath>%EPOCROOT%\epoc32\release\winscw\<urel/udeb></filepath> </p> </li> |
|
159 <li id="GUID-BFFF9550-AFA7-5097-BBE9-CE508688DA56"><p> <b>Execute the Tests:</b> </p> <p><userinput>testexecute |
|
160 z:\base\setup_<test suite name>.script</userinput> </p> <p> <filepath>setup_t_base.script</filepath> is |
|
161 used to copy the test data files on to c:\drive. </p> <p><userinput>testexecute |
|
162 c:\base\<test suite name>.script</userinput> </p> <p> <filepath>t_base.script</filepath> is |
|
163 used to run the entire base test suite. </p> </li> |
|
164 </ol> <p><b>For ARMV5 platform: </b> </p> <ol id="GUID-07FBA2B3-C3BC-5AC3-9272-4E5F87544C70"> |
|
165 <li id="GUID-9603E46B-C403-5927-9AFD-73390DB7B240"><p> <b>Build ROM image: </b> </p> <p><userinput>buildrom |
|
166 -D_EABI=ARMV5 –DRVCT -DUSE_STRONG_CRYPTOGRAPHY <h2/h4hrp> techview t_base</userinput> </p> <p>The |
|
167 ROM image is built on the PC and transferred to the hardware board through |
|
168 MMC card. <b>Note:</b> The ROM building commands is different for NAND images. |
|
169 Refer to <xref href="GUID-8D89BC22-3008-5A43-8BBC-C8F2985D71C1.dita">Base Verification |
|
170 Suite</xref> for more details. </p> </li> |
|
171 <li id="GUID-77092D52-D372-535D-B86F-0B1260B7ACB4"><p> <b>Select your Setup |
|
172 Script: </b> </p> <p>The <filepath>setup-PBASE-F32-Sfsrv-PublicApi.script</filepath> is |
|
173 used to run only F32_EKA2 validation test suite. </p> </li> |
|
174 <li id="GUID-EC2F7E9F-6848-52C8-8F2A-2A5CE6031067"><p> <b>Running Scripts:</b> </p> <p><userinput>Open |
|
175 eshell </userinput> </p> </li> |
|
176 <li id="GUID-2C31EA1C-86D0-51C2-9DE0-DDFAE32A9E8F"><p> <b>Execute the Tests:</b> </p> <p><userinput>testexecute |
|
177 z:\base\setup_<test suite name>.script</userinput> </p> <p> <filepath>setup_t_base.script</filepath> is |
|
178 used to copy the test data files on to c:\drive. </p> <p><userinput>testexecute |
|
179 c:\base\<test suite name>.script</userinput> </p> <p> <filepath>t_base.script</filepath> is |
|
180 used to run the entire base test suite. </p> </li> |
|
181 </ol> <p><b>Steps |
|
182 to build and execute tests on phone directly using .pkg file</b> </p> <p><b>For ARMV5 platform: </b> </p> <ol id="GUID-D94BEDB8-1340-59C9-B8DD-0FA2AB64FE33"> |
|
183 <li id="GUID-E29C6E42-A638-52EA-8243-EE1698786E30"><p> <b>EShell and TestExecute:</b> </p> <p>The |
|
184 phone must have eshell and testexecute installed. </p> </li> |
|
185 <li id="GUID-55FF66BC-C2B9-5CB5-97D8-3856142A4767"><p> <b> Certificate files:</b> </p> <p>Ensure <filepath>.cer</filepath> and <filepath>.key</filepath> files are placed into <filepath>/epoc32/pkg/</filepath> directory on the |
|
186 PC and rename as<filepath>zeus.cer</filepath> and <filepath>SymbianACS.key</filepath> correspondingly. </p> </li> |
|
187 <li id="GUID-657C2481-CDA1-57AE-9B5D-1F9E8DED75B2"><p> <b>Create and install |
|
188 SIS-file:</b> </p> <p>Run <filepath>makesisfiles.bat</filepath> from <filepath>/epoc32/pkg/</filepath> directory. </p> <p><userinput>makesisfiles.bat</userinput> </p> <p>This creates <filepath>t_sfsrv.sis</filepath> file. The file must |
|
189 be copied to an MMC card, transferred to the phone and executed. </p> <p>When |
|
190 the <filepath>t_sfsrv.sis</filepath> file is run, the base test suite is installed |
|
191 on the device. </p> </li> |
|
192 <li id="GUID-F6AAEEA1-77AF-5E84-8A2C-D5CB8AFC9F39"><p> <b> Running Scripts: </b> </p> <p>Run |
|
193 the test scripts. For more information refer to <xref href="GUID-3C26B5B2-1B90-5F96-9342-1D53F6EDD94F.dita#GUID-3C26B5B2-1B90-5F96-9342-1D53F6EDD94F/GUID-123789D7-482A-560A-ADAA-E2D972BB4918">Steps |
|
194 to build and execute tests manually (Tests built into ROM)</xref>. </p> </li> |
|
195 </ol> <p><b>Selective |
|
196 Execution of Test Cases using TCS File</b> </p> <p>Test cases can be excluded |
|
197 from a test run by using a <filepath>.tcs</filepath> file. The <filepath>.tcs</filepath> file |
|
198 contains IDs of test cases to be excluded. </p> <p>The test case IDs can be |
|
199 specified as a range, a list, or a combination of both. Each range or individual |
|
200 test case ID is delimited by a new-line character. </p> <p>For example, range |
|
201 of test case IDs to be excluded can be specified as: </p> <p> <codeph>pbase-f32-rfile-performance-large-0001: |
|
202 pbase-f32-rfile-performance-large-0005</codeph> </p> <p>This |
|
203 excludes all test cases from 1 to 5 (1 and 5 included) during execution. </p> <p>A |
|
204 list of test cases IDs to be excluded can be: </p> <p> <codeph>COMINF-ESOCK-RSubConnection-PublicAPI-0001</codeph> </p> <p> <codeph>COMINF-ESOCK-RSubConnection-PublicAPI-0005</codeph> </p> <p> <codeph>COMINF-ESOCK-RSubConnection-PublicAPI-0007</codeph> </p> <p>A |
|
205 combination of range and list can be: </p> <p> <codeph>pbase-f32-rfile-performance-large-0001: |
|
206 pbase-f32-rfile-performance-large-0005</codeph> </p> <p> <codeph>pbase-f32-rfile-performance-large-0010: |
|
207 pbase-f32-rfile-performance-large-0015</codeph> </p> <p> <codeph>pbase-f32-rfile-performance-large-0020</codeph> </p> <p> <codeph>pbase-f32-rfile-performance-large-0021</codeph> </p> <p>There is only one <filepath>.tcs</filepath> file located at <filepath>…\baseapitest\basesvs\config\t_base.tcs</filepath> </p> <p>For |
|
208 more information on location of <filepath>.tcs</filepath> files, see <xref href="GUID-0B240B41-652F-586A-915E-3D67BFEB8AE6.dita#GUID-0B240B41-652F-586A-915E-3D67BFEB8AE6/GUID-4FC8CBD4-02FE-566E-B739-C6EB8DDD6C48">TCS |
|
209 File Source Location</xref> in F32 Performance Test Suite, <xref href="GUID-FFDD3689-A83B-5E67-A2BD-7723B141E198.dita#GUID-FFDD3689-A83B-5E67-A2BD-7723B141E198/GUID-72714310-D4B3-5077-89C6-D7B8D4FFC5F7">TCS File Source Location</xref> in FAT32 Conformance Test Suite, and <xref href="GUID-E1EBD343-C8A6-51E5-B158-9A1D0328D3B3.dita#GUID-E1EBD343-C8A6-51E5-B158-9A1D0328D3B3/GUID-4FC8CBD4-02FE-566E-B739-C6EB8DDD6C48">TCS |
|
210 File Source Location</xref> in F32_EKA2 Validation Test Suite. </p> <p>The <filepath>.tcs</filepath> file |
|
211 must be modified when using the TestDriver for test execution. When executing |
|
212 the tests manually, the following <codeph>testexecute</codeph> command illustrates |
|
213 the usage of the <filepath>.tcs</filepath> file: </p> <p><userinput>testexecute |
|
214 %EPOCROOT%\epoc32\release\winscw\<urel/udeb>\<test suite name>.script |
|
215 –[tcx|tci] %EPOCROOT%\epoc32\release\winscw\<urel/udeb>\t_base.tcs</userinput> </p> <p>The <codeph>-tcx</codeph> switch |
|
216 is used to execute all the tests in the specified script excluding the test |
|
217 cases specified in the <filepath>.tcs</filepath> file. The <codeph>–tci</codeph> switch |
|
218 is used to execute only the tests specified in the <filepath>.tcs</filepath> file |
|
219 from the specified script. </p> <p><b>Test |
|
220 Results</b> </p> <p><b>Test |
|
221 Results log file location</b> </p> <p>After tests complete execution, result |
|
222 logs can be found on the system drive of the device in the <filepath>\logs\testexecute\</filepath> directory. </p> <p>On |
|
223 the PC, if tests are run using testdriver, results can be found in the following |
|
224 location: <filepath>%EPOCROOT%\epoc32\TestDriver\results\</filepath>. If executing |
|
225 the tests manually the results can be found in the following location: <filepath>%EPOCROOT%\epoc32\winscw\c\logs\testexecute</filepath> </p> <p>When |
|
226 using testdriver, a new test result folder is created for each test run that |
|
227 is, results are not overwritten each time a test run is run. A <filepath>.htm</filepath> log |
|
228 file for each script contained in the suite can be found in its own subfolder. </p> <p>Each |
|
229 test case in the script consists of test blocks (usually just one), which |
|
230 either pass or fail. Each test block runs some of the commands. Each of the |
|
231 commands performs an action on the tested APIs. A test block passes if all |
|
232 its commands and other instructions pass. A test case passes if all its test |
|
233 blocks pass. </p> <p>The log displays the percentage of test cases that have |
|
234 passed successfully. </p> <p><b>How |
|
235 to interpret test results</b> </p> <p>Each test suite produces its own HTML |
|
236 log file containing the results of the test run. When examining the log file, |
|
237 the results at the bottom of the log should be checked first. This gives a |
|
238 summary of the tests in the suite that have passed, failed or panicked. </p> <p>In |
|
239 the body of the log tests which passed are highlighted in green, tests which |
|
240 failed in red and tests which caused a panic in blue. The reason for any failure |
|
241 or panic is also given. </p> <p>When this test suite is run on a real device |
|
242 some tests may fail due to limitations of the device. Either the device does |
|
243 not have the correct hardware (for example, no modem exists for a test which |
|
244 needs one) or it lacks the right software plug-ins to run the test. In such |
|
245 cases the log displays that a test has failed with a -5 error (which means <codeph>KErrNotSupported</codeph>). |
|
246 Tests appearing to fail with -5 do not indicate defects, but limitations of |
|
247 the device. </p> <p>Refer to <b>Symbian Verification Suite » TestDriver » |
|
248 Using TestDriver » Results » Viewing the test results</b> for more information |
|
249 on test driver results. </p> </section> |
|
250 <section id="GUID-06D7B505-B838-4A03-9721-E8731AA0DF62"><title>OS Focussed |
|
251 Components</title> <p>The following tables illustrate the components and classes |
|
252 tested on each Symbian platform baseline: </p> <p> <b>Table 1: Validation |
|
253 testing of Base, F32_EKA2 component on each Symbian platform baseline</b> </p> <table id="GUID-2644CB3B-A76E-5ECE-B6F7-6B87829483F6"> |
|
254 <tgroup cols="6"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/><colspec colname="col3"/><colspec colname="col4"/><colspec colname="col5"/> |
|
255 <thead> |
|
256 <row> |
|
257 <entry> </entry> |
|
258 <entry> 9.1</entry> |
|
259 <entry>9.2</entry> |
|
260 <entry>9.3 </entry> |
|
261 <entry>9.4</entry> |
|
262 <entry>9.5</entry> |
|
263 </row> |
|
264 <row> |
|
265 <entry> RFs </entry> |
|
266 </row> |
|
267 <row> |
|
268 <entry> CDir </entry> |
|
269 </row> |
|
270 <row> |
|
271 <entry> CDirScan </entry> |
|
272 </row> |
|
273 <row> |
|
274 <entry> CFileBase </entry> |
|
275 </row> |
|
276 <row> |
|
277 <entry> CFileMan </entry> |
|
278 </row> |
|
279 <row> |
|
280 <entry> MFileManObserver </entry> |
|
281 </row> |
|
282 <row> |
|
283 <entry> RDir </entry> |
|
284 </row> |
|
285 <row> |
|
286 <entry> RFile </entry> |
|
287 </row> |
|
288 <row> |
|
289 <entry> RFormat </entry> |
|
290 </row> |
|
291 <row> |
|
292 <entry> RRawDisk </entry> |
|
293 </row> |
|
294 <row> |
|
295 <entry> TDriveUnit </entry> |
|
296 </row> |
|
297 <row> |
|
298 <entry> TEntry </entry> |
|
299 </row> |
|
300 <row> |
|
301 <entry> TEntryArray </entry> |
|
302 </row> |
|
303 <row> |
|
304 <entry> TFindFile </entry> |
|
305 </row> |
|
306 <row> |
|
307 <entry> TFileText </entry> |
|
308 </row> |
|
309 <row> |
|
310 <entry> TOpenFileScan </entry> |
|
311 </row> |
|
312 <row> |
|
313 <entry> TParse </entry> |
|
314 </row> |
|
315 <row> |
|
316 <entry> TParseBase </entry> |
|
317 </row> |
|
318 <row> |
|
319 <entry> TParsePtr </entry> |
|
320 </row> |
|
321 <row> |
|
322 <entry> TparsePtrC </entry> |
|
323 </row> |
|
324 <row> |
|
325 <entry> TVolumeInfo </entry> |
|
326 </row> |
|
327 <row> |
|
328 <entry> FileNamesIdentical() </entry> |
|
329 </row> |
|
330 </thead> |
|
331 <tbody> |
|
332 <row> |
|
333 <entry><p>X </p> </entry> |
|
334 <entry><p>X </p> </entry> |
|
335 <entry><p>X </p> </entry> |
|
336 <entry><p>X </p> </entry> |
|
337 <entry><p>X </p> </entry> |
|
338 </row> |
|
339 <row> |
|
340 <entry/> |
|
341 <entry/> |
|
342 <entry/> |
|
343 <entry><p>X </p> </entry> |
|
344 <entry><p>X </p> </entry> |
|
345 </row> |
|
346 <row> |
|
347 <entry/> |
|
348 <entry/> |
|
349 <entry/> |
|
350 <entry><p>X </p> </entry> |
|
351 <entry><p>X </p> </entry> |
|
352 </row> |
|
353 <row> |
|
354 <entry/> |
|
355 <entry/> |
|
356 <entry/> |
|
357 <entry><p>X </p> </entry> |
|
358 <entry><p>X </p> </entry> |
|
359 </row> |
|
360 <row> |
|
361 <entry/> |
|
362 <entry/> |
|
363 <entry/> |
|
364 <entry><p>X </p> </entry> |
|
365 <entry><p>X </p> </entry> |
|
366 </row> |
|
367 <row> |
|
368 <entry/> |
|
369 <entry/> |
|
370 <entry/> |
|
371 <entry><p>X </p> </entry> |
|
372 <entry><p>X </p> </entry> |
|
373 </row> |
|
374 <row> |
|
375 <entry/> |
|
376 <entry/> |
|
377 <entry/> |
|
378 <entry><p>X </p> </entry> |
|
379 <entry><p>X </p> </entry> |
|
380 </row> |
|
381 <row> |
|
382 <entry/> |
|
383 <entry/> |
|
384 <entry/> |
|
385 <entry><p>X </p> </entry> |
|
386 <entry><p>X </p> </entry> |
|
387 </row> |
|
388 <row> |
|
389 <entry/> |
|
390 <entry/> |
|
391 <entry/> |
|
392 <entry><p>X </p> </entry> |
|
393 <entry><p>X </p> </entry> |
|
394 </row> |
|
395 <row> |
|
396 <entry/> |
|
397 <entry/> |
|
398 <entry/> |
|
399 <entry><p>X </p> </entry> |
|
400 <entry><p>X </p> </entry> |
|
401 </row> |
|
402 <row> |
|
403 <entry/> |
|
404 <entry/> |
|
405 <entry/> |
|
406 <entry><p>X </p> </entry> |
|
407 <entry><p>X </p> </entry> |
|
408 </row> |
|
409 <row> |
|
410 <entry/> |
|
411 <entry/> |
|
412 <entry/> |
|
413 <entry><p>X </p> </entry> |
|
414 <entry><p>X </p> </entry> |
|
415 </row> |
|
416 <row> |
|
417 <entry/> |
|
418 <entry/> |
|
419 <entry/> |
|
420 <entry><p>X </p> </entry> |
|
421 <entry><p>X </p> </entry> |
|
422 </row> |
|
423 <row> |
|
424 <entry/> |
|
425 <entry/> |
|
426 <entry/> |
|
427 <entry><p>X </p> </entry> |
|
428 <entry><p>X </p> </entry> |
|
429 </row> |
|
430 <row> |
|
431 <entry/> |
|
432 <entry/> |
|
433 <entry/> |
|
434 <entry><p>X </p> </entry> |
|
435 <entry><p>X </p> </entry> |
|
436 </row> |
|
437 <row> |
|
438 <entry/> |
|
439 <entry/> |
|
440 <entry/> |
|
441 <entry><p>X </p> </entry> |
|
442 <entry><p>X </p> </entry> |
|
443 </row> |
|
444 <row> |
|
445 <entry/> |
|
446 <entry/> |
|
447 <entry/> |
|
448 <entry><p>X</p> </entry> |
|
449 <entry><p>X </p> </entry> |
|
450 </row> |
|
451 <row> |
|
452 <entry/> |
|
453 <entry/> |
|
454 <entry/> |
|
455 <entry><p>X</p> </entry> |
|
456 <entry><p>X </p> </entry> |
|
457 </row> |
|
458 <row> |
|
459 <entry/> |
|
460 <entry/> |
|
461 <entry/> |
|
462 <entry><p>X</p> </entry> |
|
463 <entry><p>X </p> </entry> |
|
464 </row> |
|
465 <row> |
|
466 <entry/> |
|
467 <entry/> |
|
468 <entry/> |
|
469 <entry><p>X</p> </entry> |
|
470 <entry><p>X </p> </entry> |
|
471 </row> |
|
472 <row> |
|
473 <entry/> |
|
474 <entry/> |
|
475 <entry/> |
|
476 <entry><p>X</p> </entry> |
|
477 <entry><p>X </p> </entry> |
|
478 </row> |
|
479 <row> |
|
480 <entry/> |
|
481 <entry/> |
|
482 <entry/> |
|
483 <entry><p>X</p> </entry> |
|
484 <entry><p>X </p> </entry> |
|
485 </row> |
|
486 </tbody> |
|
487 </tgroup> |
|
488 </table> <p> <b>Table 2: Performance testing of Base, F32_EKA2 on each Symbian |
|
489 platform baseline</b> </p> <table id="GUID-A1F0DEB7-41D7-548A-96A9-9731D54FBD1E"> |
|
490 <tgroup cols="6"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/><colspec colname="col3"/><colspec colname="col4"/><colspec colname="col5"/> |
|
491 <thead> |
|
492 <row> |
|
493 <entry> </entry> |
|
494 <entry> 9.1</entry> |
|
495 <entry>9.2</entry> |
|
496 <entry>9.3 </entry> |
|
497 <entry>9.4</entry> |
|
498 <entry>9.5</entry> |
|
499 </row> |
|
500 <row> |
|
501 <entry>RFs</entry> |
|
502 </row> |
|
503 <row> |
|
504 <entry>RFile</entry> |
|
505 </row> |
|
506 </thead> |
|
507 <tbody> |
|
508 <row> |
|
509 <entry><p>X </p> </entry> |
|
510 <entry><p>X </p> </entry> |
|
511 <entry><p>X </p> </entry> |
|
512 <entry><p>X </p> </entry> |
|
513 <entry><p>X</p> </entry> |
|
514 </row> |
|
515 <row> |
|
516 <entry><p>X </p> </entry> |
|
517 <entry><p>X </p> </entry> |
|
518 <entry><p>X </p> </entry> |
|
519 <entry><p>X </p> </entry> |
|
520 <entry><p>X</p> </entry> |
|
521 </row> |
|
522 </tbody> |
|
523 </tgroup> |
|
524 </table> <p>The FAT32 conformance test suite is not API specific and is available |
|
525 on Symbian platform versions 9.4 and 9.5. </p> </section> |
|
526 </conbody></concept> |