T_Camera -test suite

This topic describes the T_Camera Test Suite. It provides -an overview about the test suite, its coverage, how to set up the test environment -to execute the test suite, and how to find further information about the test -cases offered by this test suite.

Test Suite overview

The T_Camera Test -Suite provides the tests for the CCamera class.

All -APIs that Symbian classifies as PublishedAll are tested within this -class.

Note: Any mention of epoc32 is offset -by %EPOCROOT% that is, the full path where the epoc tree -is installed.

Test approach

The Test Suite provides a basic run -through of the public functionality of the CCamera API. -The purpose of the Test Suite is to provide a regression test suite of PublishedAll -APIs for CCamera class. Negative testing is performed wherever -it is needed, to confirm that correct errors are returned when incorrect parameters -are given. The tests are automated and does not require user intervention.

Coverage omissions

None.

Test suite details

Test Script Source -Tree location:

The descriptions of the test cases can be found -in the following location:

…\os\mm\mmapitest\mmsvs\suite\ecam\t_camera\scripts\MM-ECM-PublicApi.script
Test Script EPOC -tree location on Emulator:

When the tests are built for emulator -or hardware (winscw or armv5), the scripts are exported to the following location -in the epoc tree:

%EPOCROOT%\epoc32\data\Z\multimedia
Test Script Hardware -path location:

When the tests are built, the scripts are built -in the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia

Note: If the tests are built to run on hardware, the files are built in the z drive -of the ROM.

Test -data source tree location

The test data files can be found in -the following location:

…\os\mm\mmapitest\mmsvs\suite\ecam\testdata\t_camera\MM-ECM-PublicApi.ini

…\os\mm\mmapitest\mmsvs\suite\testdata\t_multimedia.ini

Test data EPOC tree location

When the tests are built for -emulator or hardware (winscw or armv5), the test data files are exported to -the following location in the epoc tree:

%EPOCROOT%\epoc32\data\Z\multimedia\MM-ECM-PublicApi.ini

%EPOCROOT%\epoc32\data\Z\multimedia\t_multimedia.ini

Test -Data Build Location

When the tests are built, the test data files -are built in the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia -

Note: If the tests are built -to run on hardware, the files are built in the z drive of -the ROM.

TestDriver file

The multimedia .driver file -is found in the following location:

…\os\mm\mmapitest\mmsvs\suite\testsuites\multimedia

This -is used by the TestDriver to construct the test suite tree structure and export -all the appropriate files to the correct location in the epoc32 tree and on -the device.

When the tests are built, the .driver file -is built in the following location:

%EPOCROOT%\epoc32\testdriver\testproduct

TCS file source location

The .tcs file -can be found in the following location:

…\os\mm\mmapitest\mmsvs\suite\config\t_multimedia.tcs

TCS file build location

When the tests are built, the .tcs file -is generated into the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia

Note: When the tests are built to be executed on the hardware, -the files are built into the z drive of the ROM.

Test global environment -file

The t_multimedia.ini file is the test -suite global environment file that contains the following configurable parameters -in default_camera section:

count = 1

Defines -the number of cameras available on the device.
validstill -= 0

Sets to the 0 offset index of the camera used for still -photography tests.
invalidstill -= 100

Sets to an invalid camera index for negative still -photography tests.

This enables you to modify these parameter values so that the tests -may be executed with different test data. For example, if the device under -test has 2 cameras, then count = 2.

Test environment and execution

Device -setup

The device under test must have the camera hardware in place. -The Symbian platform does not provide an implementation of the CCamera class -assuming that device creators are likely to have their own cameras.

The -device specific camera details can be modified in the t_multimedia.ini file. -(refer to Test -global environment file section).

The test suite can be run -using the test camera application in the absence of a production quality camera -application. The test camera implements the complete set of API functionality. -However, a device creator may not implement all API functionality and consequently -tests for unimplemented APIs will fail. The test camera application can be -found in the following location (relative to the location of the source code):

…\os\mm\imagingandcamerafws\camerafw

The following commands in mmsetup.pl file builds -the test camera:

system("bldmake bldfiles"); -system("abld test build $platform $build testcamera"); -

…\mmapitest\mmsvs\suite\group\mmsetup.pl

This -can be run by running mmsetup.bat.

In addition -an empty file 102070CC.txt must be created on the same -drive \epoc32\winscw\c\

For information on test -environment and build and execution procedure, refer to Multimedia -test technology.

Support

For support issues related to this Test Suite description and issues -to running the tests, test pass rates, and potential defects, contact Symbian -or your SDK provider. In most instances this will be either through the Symbian -technical consulting teams, the SDK provider forums or via the developer area -of Symbian website.

+ + + + + +T_Camera +test suite +

This topic describes the T_Camera Test Suite. It provides +an overview about the test suite, its coverage, how to set up the test environment +to execute the test suite, and how to find further information about the test +cases offered by this test suite.

Test Suite overview

The T_Camera Test +Suite provides the tests for the CCamera class.

All +APIs that Symbian classifies as PublishedAll are tested within this +class.

Note: Any mention of epoc32 is offset +by %EPOCROOT% that is, the full path where the epoc tree +is installed.

Test approach

The Test Suite provides a basic run +through of the public functionality of the CCamera API. +The purpose of the Test Suite is to provide a regression test suite of PublishedAll +APIs for CCamera class. Negative testing is performed wherever +it is needed, to confirm that correct errors are returned when incorrect parameters +are given. The tests are automated and does not require user intervention.

Coverage omissions

None.

Test suite details

Test Script Source +Tree location:

The descriptions of the test cases can be found +in the following location:

…\os\mm\mmapitest\mmsvs\suite\ecam\t_camera\scripts\MM-ECM-PublicApi.script
Test Script EPOC +tree location on Emulator:

When the tests are built for emulator +or hardware (winscw or armv5), the scripts are exported to the following location +in the epoc tree:

%EPOCROOT%\epoc32\data\Z\multimedia
Test Script Hardware +path location:

When the tests are built, the scripts are built +in the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia

Note: If the tests are built to run on hardware, the files are built in the z drive +of the ROM.

Test +data source tree location

The test data files can be found in +the following location:

…\os\mm\mmapitest\mmsvs\suite\ecam\testdata\t_camera\MM-ECM-PublicApi.ini

…\os\mm\mmapitest\mmsvs\suite\testdata\t_multimedia.ini

Test data EPOC tree location

When the tests are built for +emulator or hardware (winscw or armv5), the test data files are exported to +the following location in the epoc tree:

%EPOCROOT%\epoc32\data\Z\multimedia\MM-ECM-PublicApi.ini

%EPOCROOT%\epoc32\data\Z\multimedia\t_multimedia.ini

Test +Data Build Location

When the tests are built, the test data files +are built in the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia +

Note: If the tests are built +to run on hardware, the files are built in the z drive of +the ROM.

TestDriver file

The multimedia .driver file +is found in the following location:

…\os\mm\mmapitest\mmsvs\suite\testsuites\multimedia

This +is used by the TestDriver to construct the test suite tree structure and export +all the appropriate files to the correct location in the epoc32 tree and on +the device.

When the tests are built, the .driver file +is built in the following location:

%EPOCROOT%\epoc32\testdriver\testproduct

TCS file source location

The .tcs file +can be found in the following location:

…\os\mm\mmapitest\mmsvs\suite\config\t_multimedia.tcs

TCS file build location

When the tests are built, the .tcs file +is generated into the following location:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\multimedia

Note: When the tests are built to be executed on the hardware, +the files are built into the z drive of the ROM.

Test global environment +file

The t_multimedia.ini file is the test +suite global environment file that contains the following configurable parameters +in default_camera section:

count = 1

Defines +the number of cameras available on the device.
validstill += 0

Sets to the 0 offset index of the camera used for still +photography tests.
invalidstill += 100

Sets to an invalid camera index for negative still +photography tests.

This enables you to modify these parameter values so that the tests +may be executed with different test data. For example, if the device under +test has 2 cameras, then count = 2.

Test environment and execution

Device +setup

The device under test must have the camera hardware in place. +The Symbian platform does not provide an implementation of the CCamera class +assuming that device creators are likely to have their own cameras.

The +device specific camera details can be modified in the t_multimedia.ini file. +(refer to Test +global environment file section).

The test suite can be run +using the test camera application in the absence of a production quality camera +application. The test camera implements the complete set of API functionality. +However, a device creator may not implement all API functionality and consequently +tests for unimplemented APIs will fail. The test camera application can be +found in the following location (relative to the location of the source code):

…\os\mm\imagingandcamerafws\camerafw

The following commands in mmsetup.pl file builds +the test camera:

system("bldmake bldfiles"); +system("abld test build $platform $build testcamera"); +

…\mmapitest\mmsvs\suite\group\mmsetup.pl

This +can be run by running mmsetup.bat.

In addition +an empty file 102070CC.txt must be created on the same +drive \epoc32\winscw\c\

For information on test +environment and build and execution procedure, refer to Multimedia +test technology.

Support

For support issues related to this Test Suite description and issues +to running the tests, test pass rates, and potential defects, contact Symbian +or your SDK provider. In most instances this will be either through the Symbian +technical consulting teams, the SDK provider forums or via the developer area +of Symbian website.

\ No newline at end of file