This topic describes the BitGDI Graphics test suite and explains how to set up the test environment.
Note: Any mention to epoc32 is offset by %EPOCROOT%, which is the full path to where the epoc tree is installed.
The BitGDI test suite provides regression test suites for the following classes:
The purpose of the test suite is to provide regression testing of the public (PublishedAll) APIs of the BitGDI classes. The testing includes negative testing to confirm that the correct errors are returned when incorrect parameters are provided. The tests are automated and do not require user intervention.
None.
Test script source tree location
Descriptions of the test cases can be found in the test scripts in the following locations:
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-PolygonFiller-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsDevice-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsScreenDevice-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsBitmapDevice-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsBitGc-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsBitGcFont-PublicApi.script
...\graphics\graphicsapitest\bitgdi\scripts\GRAPHICS-BITGDI-FbsBitGcBitmap-PublicApi.script
Test script EPOC tree location
When the tests are built for emulator or hardware (winscw/armv5), the scripts are exported to the following location:
%EPOCROOT%\epoc32\data\Z\graphics\
Test script build location
When the tests are built, the scripts are built into the following location:
%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\graphics
Note: When the tests are built to be executed on hardware, the files are built into the z: drive of the ROM.
Test data source tree location
The test suite contains the following test data files:
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-PolygonFiller-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsDevice-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsScreenDevice-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI -FbsBitmapDevice-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsBitGc-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsBitGc-PublicApi-2.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsBitGc-PublicApi-3.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsBitGcFont-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\GRAPHICS-BITGDI-FbsBitGcBitmap-PublicApi.ini
...\graphics\graphicsapitest\graphicssvs\bitgdi\testdata\test_rwssprite_bitmap.mbm
The global environment file is located in the following location:
...\graphics\graphicsapitest\graphicssvs\testdata\<platform>\t_graphics.ini
Where <platform> can be armv5 or winscw.
Test data files EPOC tree location
When the tests are built for the emulator or hardware (winscw or armv5), the data files are exported to the following location:
%EPOCROOT%\epoc32\data\Z\graphics\
The global environment file, t_graphics.ini is located in the following location:
%EPOCROOT%\epoc32\data\Z\graphics\<platform>\
Where <platform> can be armv5 or winscw.
Test data files emulator location
When the tests are built, the test data (.ini) files (with the exception of the global environment file, t_graphics.ini) are built into the following location:
%EPOCROOT%\epoc32\release\<platform>\<udeb/urel>\Z\graphics\
The global environment file, t_graphics.ini, is built in the following location:
%EPOCROOT%\epoc32\release\<platform>\<udeb/urel>\Z\graphics\<platform>
Where <platform> can be armv5 or winscw.
Note: When the tests are built to be executed on hardware the files are built into the z: drive of the ROM.
Test .driver file
The graphics.driver file can be found in the following path:
...\graphics\graphicsapitest\graphicssvs\testsuites\graphics\
It is used by 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 can be found in the following location:
%EPOCROOT%\epoc32\testdriver\testproduct
TCS files source tree location
The .tcs files can be found in the following location:
...\graphics\graphicsapitest\graphicssvs\config\t_graphics.tcs
...\graphics\graphicsapitest\graphicssvs\config\t_graphics_panic.tcs
TCS files build location
When the tests are built, the scripts are generated in the following location:
%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\graphics
Note: When the tests are built to be executed on hardware, the files are built into the z: drive of the ROM.
For information about the test environment and execution procedure, see Graphics Test Technology.
Excluding panicking test cases
Some of the negative test cases, which check for panic codes, cause other positive test cases to fail. Therefore, these test cases are excluded from normal execution by specifying the test case IDs in the t_graphics_panic.tcs file.
When using test driver to execute the test suite:
graphics.panicless.bitgdi executes the specified suite excluding the listed test cases
graphics.panic.bitgdi executes the tests that panic.
When executing the tests manually, the following test execute command illustrates the usage of the .tcs file:
testexecute %EPOCROOT%\epoc32\release\winscw\<urel/udeb>\<test suite name>.script –[tcx|tci] %EPOCROOT%\epoc32\release\winscw\<urel/udeb>\< t_graphics.tcs|t_graphics_panic.tcs>.tcs
The -tcx switch is used to execute all the tests in the specified script excluding the test cases specified in the .tcs file. While the –tci switch is used to execute only the tests specified in the .tcs file from the specified script. For more information, see Graphics Test Technology.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.