Share via


Compact Database Build Verification Test (Compact 2013)

3/26/2014

The CEDB Build Verification test uncovers common API and functionality problems with CEDB and the file system.

The test suite covers the following CEDB methods:

  • CeCreateDatabaseEx
  • CeOpenDatabaseEx
  • CeOidGetInfoEx
  • CeDeleteDatabaseEx
  • CeFindFirstDatabaseEx
  • CeFindNextDatabaseEx
  • CeSeekDatabase
  • CeReadRecordPropsEx
  • CeWriteRecordProps

This test library is built from the same source code as the EDB Build Verification test, but they are built differently. Some database functionalities have to call a different API between CEDB and EDB.

You may want to run this test each time you make a custom build, to uncover any database-related issues caused by regressions.

Test Prerequisites

Your device must meet the following requirements before you run this test.

There are no hardware requirements for the CEDB Build Verification test.

The following table shows the software requirements for the CEDB Build Verification test.

Requirement

Description

Tux.exe

Test harness, required for executing the test

Kato.dll

Logging engine, required for logging test data

Cedbtst.dll

Test library

Note: There must be at least 0.5 MB of free space in the root directory of the target device. If there is not sufficient space in the root directory of the device, the test cannot run properly. An alternate option is to run the test suite on a storage media such as a storage card or hard disk.

Subtests

The following table lists the subtests included in this test.

SubTest ID

Description

1001

Creates, deletes, opens, and closes databases.

1002

Tests finding the database.

1003

Reads, writes, seeks, and deletes records from a database.

Setting Up the Test

This test has no additional requirements beyond the standard test environment setup.

Running the Test

The CEDB Build Verification test executes the tux -o -d cedbtst command line on default execution.

Verifying the Test

When the test completes, verify that "PASS" appears in the test log for all subtests.

Troubleshooting the Test

Ensure that there is enough storage space on the root directory. If there is not, this test cannot run properly.

See Also

Other Resources

File System Tests