Kernel +Tests Guide

Purpose

The +kernel tests provide performance bench marking for kernel and peripheral devices +and ensures that all required components are working as expected.

Building a +test

Tests are built using the Symbian ROM build utility.

A +handy script has been produced to simplify test building:

To build +a series of automatic tests execute rom.bat, found in \e32\rombuild. +You will need to set the attributes and options to tell the system which tests +to run.

For example, to build a debug MISA ROM image, using the ARM4 +Instruction set, containing both the E32Test and F32Test tests, enter:

cd \e32\rombuild

rom --assp =misa --inst =arm4 --build =urel --type =alltests

Which +creates misabaarm4.img, rombuild.log and rom.oby in \e32\rombuild. The *.img image file should be renamed and then transferred +to the target hardware as appropriate for the target device.

Test +configuration can be customized by editing e32test\group\bld.inf and +adding or removing device drivers or kernel tests as required. All tests included +in the default build are part of the automatic test, those marked as manual +need to be explicitly included.

Executing tests

The +kernel tests can be built and executed as automatic or manual tests.

Automatic test

Tests +flagged as automatic are built into test scripts, which are then built into +the ROM image.
Manual test

Some +of the manual tests do not produce the log data via serial port which is indicated +in the test reference document. The successful completion of these tests should +be verified by monitoring the screen output, rather than referring to the +log data at the end of a testing session.

Verification +of the test results

Automatic test

All automatic +tests output a log file via serial port. Such output should be captured using +HyperTerminal or a tool with similar functionality. Each test uses the RTest class +which is part of the EPOC base. The log data output is specific to the test, +however there are few elements of the output that are similar across all tests.

If +the output generated by RTest shows

FAIL : T_DSPACE failed check 1 at line Number: 660

it means a particular test case in the test program has failed. The line +and check number of the failed test case is displayed. This will help to track +the defect in the test code.

If the output generated by RTest shows

RTEST: SUCCESS : T_OPEN test completed O.K.

it +means the test is successful.

Manual test

For manual +tests that output log file the procedure is the same as explained above. For +tests that do not output serial logs, successful completion of the test should +be verified by monitoring the screen output. Since these tests are still RTest +based the output will still follow the patterns outlined above.