|
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-89A4937C-79C6-5985-9275-496A4299F30F" xml:lang="en"><title>T_Camera |
|
13 test suite </title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>This topic describes the <codeph>T_Camera</codeph> Test Suite. It provides |
|
15 an overview about the test suite, its coverage, how to set up the test environment |
|
16 to execute the test suite, and how to find further information about the test |
|
17 cases offered by this test suite. </p> |
|
18 <section><title>Test Suite overview</title> <p>The <codeph>T_Camera</codeph> Test |
|
19 Suite provides the tests for the <xref href="GUID-021C509B-C821-3401-B2F4-DE7F52BB16D4.dita"><apiname>CCamera</apiname></xref> class. </p> <p>All |
|
20 APIs that Symbian classifies as <b>PublishedAll</b> are tested within this |
|
21 class. </p> <p> <b>Note:</b> Any mention of <codeph>epoc32</codeph> is offset |
|
22 by <codeph>%EPOCROOT%</codeph> that is, the full path where the epoc tree |
|
23 is installed. </p> </section> |
|
24 <section><title>Test approach</title> <p>The Test Suite provides a basic run |
|
25 through of the public functionality of the <xref href="GUID-021C509B-C821-3401-B2F4-DE7F52BB16D4.dita"><apiname>CCamera</apiname></xref> API. |
|
26 The purpose of the Test Suite is to provide a regression test suite of PublishedAll |
|
27 APIs for <xref href="GUID-021C509B-C821-3401-B2F4-DE7F52BB16D4.dita"><apiname>CCamera</apiname></xref> class. Negative testing is performed wherever |
|
28 it is needed, to confirm that correct errors are returned when incorrect parameters |
|
29 are given. The tests are automated and does not require user intervention. </p> </section> |
|
30 <section><title>Coverage omissions</title> <p>None. </p> </section> |
|
31 <section><title>Test suite details</title> <ul> |
|
32 <li id="GUID-35CA0F2A-797D-5267-8EDD-D8475D8A38E4"><p> <b>Test Script Source |
|
33 Tree location:</b> </p> <p>The descriptions of the test cases can be found |
|
34 in the following location: </p> <p> <filepath>…\os\mm\mmapitest\mmsvs\suite\ecam\t_camera\scripts\MM-ECM-PublicApi.script</filepath> </p> </li> |
|
35 <li id="GUID-498A9781-5525-58F3-8063-E4BA4ED53ED4"><p> <b>Test Script EPOC |
|
36 tree location on Emulator:</b> </p> <p>When the tests are built for emulator |
|
37 or hardware (winscw or armv5), the scripts are exported to the following location |
|
38 in the epoc tree: </p> <p><filepath>%EPOCROOT%\epoc32\data\Z\multimedia</filepath> </p> </li> |
|
39 <li id="GUID-75A55F11-D616-5C0F-BDDE-972295E29418"><p> <b>Test Script Hardware |
|
40 path location: </b> </p> <p>When the tests are built, the scripts are built |
|
41 in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia</filepath> </p> <p> <b>Note: </b> If the tests are built to run on hardware, the files are built in the <codeph>z</codeph> drive |
|
42 of the ROM. </p> </li> |
|
43 </ul> <p><b>Test |
|
44 data source tree location</b> </p> <p>The test data files can be found in |
|
45 the following location: </p> <p> <filepath>…\os\mm\mmapitest\mmsvs\suite\ecam\testdata\t_camera\MM-ECM-PublicApi.ini</filepath> </p> <p> <filepath>…\os\mm\mmapitest\mmsvs\suite\testdata\t_multimedia.ini</filepath> </p> <p><b>Test data EPOC tree location</b> </p> <p>When the tests are built for |
|
46 emulator or hardware (winscw or armv5), the test data files are exported to |
|
47 the following location in the epoc tree: </p> <p> <filepath>%EPOCROOT%\epoc32\data\Z\multimedia\MM-ECM-PublicApi.ini</filepath> </p> <p> <filepath>%EPOCROOT%\epoc32\data\Z\multimedia\t_multimedia.ini</filepath> </p> <p><b>Test |
|
48 Data Build Location</b> </p> <p>When the tests are built, the test data files |
|
49 are built in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia |
|
50 </filepath> </p> <p> <b>Note: </b> If the tests are built |
|
51 to run on hardware, the files are built in the <codeph>z</codeph> drive of |
|
52 the ROM. </p> <p><b>TestDriver file</b> </p> <p>The multimedia <filepath>.driver</filepath> file |
|
53 is found in the following location: </p> <p> <filepath>…\os\mm\mmapitest\mmsvs\suite\testsuites\multimedia </filepath> </p> <p>This |
|
54 is used by the TestDriver to construct the test suite tree structure and export |
|
55 all the appropriate files to the correct location in the epoc32 tree and on |
|
56 the device. </p> <p>When the tests are built, the <filepath>.driver</filepath> file |
|
57 is built in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\testdriver\testproduct</filepath> </p> <p id="GUID-20A11B22-C8ED-59CB-81C0-27C06A237F36"><b>TCS file source location</b> </p> <p>The <filepath>.tcs</filepath> file |
|
58 can be found in the following location: </p> <p> <filepath>…\os\mm\mmapitest\mmsvs\suite\config\t_multimedia.tcs</filepath> </p> <p><b>TCS file build location</b> </p> <p>When the tests are built, the <filepath>.tcs</filepath> file |
|
59 is generated into the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia</filepath> </p> <p> <b>Note:</b> When the tests are built to be executed on the hardware, |
|
60 the files are built into the <filepath>z</filepath> drive of the ROM. </p> <p id="GUID-A87D9A93-BDD3-5443-8C3D-B36221AE0A39"><b>Test global environment |
|
61 file</b> </p> <p>The <filepath>t_multimedia.ini</filepath> file is the test |
|
62 suite global environment file that contains the following configurable parameters |
|
63 in <codeph>default_camera</codeph> section: </p> <ul> |
|
64 <li id="GUID-0988BEF7-CFF6-5575-8172-C89A282CCAC6"><p> <codeph>count = 1</codeph> </p> <p>Defines |
|
65 the number of cameras available on the device. </p> </li> |
|
66 <li id="GUID-4304AFA7-7507-563F-8B92-08FC1EFF05AF"><p> <codeph>validstill |
|
67 = 0</codeph> </p> <p>Sets to the 0 offset index of the camera used for still |
|
68 photography tests. </p> </li> |
|
69 <li id="GUID-F7303127-15E2-571B-94A4-05E3A1C16D66"><p> <codeph>invalidstill |
|
70 = 100</codeph> </p> <p>Sets to an invalid camera index for negative still |
|
71 photography tests. </p> </li> |
|
72 </ul> <p>This enables you to modify these parameter values so that the tests |
|
73 may be executed with different test data. For example, if the device under |
|
74 test has 2 cameras, then <codeph>count = 2</codeph>. </p> </section> |
|
75 <section><title>Test environment and execution</title> <p><b>Device |
|
76 setup</b> </p> <p>The device under test must have the camera hardware in place. |
|
77 The Symbian platform does not provide an implementation of the <codeph>CCamera</codeph> class |
|
78 assuming that device creators are likely to have their own cameras. </p> <p>The |
|
79 device specific camera details can be modified in the <filepath>t_multimedia.ini</filepath> file. |
|
80 (refer to <xref href="GUID-89A4937C-79C6-5985-9275-496A4299F30F.dita#GUID-89A4937C-79C6-5985-9275-496A4299F30F/GUID-A87D9A93-BDD3-5443-8C3D-B36221AE0A39">Test |
|
81 global environment file</xref> section). </p> <p>The test suite can be run |
|
82 using the test camera application in the absence of a production quality camera |
|
83 application. The test camera implements the complete set of API functionality. |
|
84 However, a device creator may not implement all API functionality and consequently |
|
85 tests for unimplemented APIs will fail. The test camera application can be |
|
86 found in the following location (relative to the location of the source code): </p> <p> <filepath>…\os\mm\imagingandcamerafws\camerafw</filepath> </p> <p>The following commands in <filepath>mmsetup.pl</filepath> file builds |
|
87 the test camera: </p> <codeblock id="GUID-2F3B150E-F152-5279-84DC-86B563EEDBB3" xml:space="preserve">system("bldmake bldfiles"); |
|
88 system("abld test build $platform $build testcamera"); |
|
89 </codeblock> <p> <filepath>…\mmapitest\mmsvs\suite\group\mmsetup.pl </filepath> </p> <p>This |
|
90 can be run by running <filepath>mmsetup.bat</filepath>. </p> <p>In addition |
|
91 an empty file <filepath>102070CC.txt</filepath> must be created on the same |
|
92 drive <filepath>\epoc32\winscw\c\</filepath> </p> <p>For information on test |
|
93 environment and build and execution procedure, refer to <xref href="GUID-05570195-D64A-5F65-AB7C-2C6BF8D332B3.dita">Multimedia |
|
94 test technology</xref>. </p> <p><b>Support</b> </p> <p>For support issues related to this Test Suite description and issues |
|
95 to running the tests, test pass rates, and potential defects, contact Symbian |
|
96 or your SDK provider. In most instances this will be either through the Symbian |
|
97 technical consulting teams, the SDK provider forums or via the developer area |
|
98 of <xref href="http:\\www.Symbian.org" scope="external">Symbian</xref> website. </p> </section> |
|
99 </conbody></concept> |