EDB Build Verification Test (Compact 2013)
3/26/2014
The EDB (Embedded Database) Build Verification Test uncovers common API and functionality problems with EDB and the file system.
The test suite covers the following EDB methods:
CeCreateDatabaseEx2
CeOpenDatabaseEx2
CeDeleteDatabaseEx
CeFindFirstDatabaseEx
CeFindNextDatabaseEx
CeSeekDatabase
CeReadRecordPropsEx
CeWriteRecordProps
This test library is built from the same source code as the CEDB 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 EDB Build Verification Test.
The following table shows the software requirements for the EDB Build Verification Test.
Requirement |
Description |
|---|---|
Tux.exe |
Test harness, required for executing the test. |
Kato.dll |
Logging engine, required for logging test data. |
edbtst.dll |
Test library. |
Note: There must be at least 0.5 megabytes (MB) of free space in the root directory of the target device. If there is not sufficient space in the root directory of the target device, the test cannot run properly.
Subtests
The table below 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 EDB Build Verification Test executes the tux -o -d edbtst command line on default execution.
The following table shows the optional command line parameter for the EDB Build Verification Test.
Command line parameter |
Description |
|---|---|
-x test_case_ID |
Specifies which test case to run. |
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log for all subtests.
Troubleshooting the Test
There must be at least 0.5 megabytes (MB) of free space in the root directory of the target device. If there is not sufficient space in the root directory of the target device, the test cannot run properly.