Two sets of conformance tests are included in this version of the MDAC SDK: OLE DB interface tests and ADO minimal tests. They are located in the MDAC installation directory under \Conformance\Tests. For complete file and path information, see Files Used for Conformance Testing in this guide.
You can use the TableDump utility to build your own tests. The files generated from this utility identify provider-specific information.
Sample test modules are available but only as examples of test code. They are not supported.
The OLE DB interface tests check providers' compliance to standards in the OLE DB Programmer's Reference.
OLE DB leveling identifies the critical interfaces and behaviors (properties) required for providers and expected by consumers. Conformance testing of these interfaces identifies base consumer functionality and minimum provider functionality, which helps you write applications that support the natural functionality of native data stores and that extend built-in services. (For more information about OLE DB leveling, see the technical article OLE DB Leveling: Choosing the Right Interfaces.)
The OLE DB interface tests were originally written to test the Microsoft OLE DB Provider for ODBC Drivers, which is also included in the MDAC SDK. The Level 0 (minimum) provider interfaces have been modified to handle a wide range of providers and are located in the \Proposed subdirectory.
Only the Level 0 (minimum) interface tests are supported. Tests for the other interfaces are available in the \Unsupported subdirectory.
The ADO minimal tests are a small set of tests, at least one per ADO method, which check whether ADO statements work correctly against a provider. There are tests for each ADO method, including methods used for updates and for transactions. The tests are grouped so that you can run just the Level 0 tests, which do not require updatability or transactions; or you can run the full set of ADO tests.
The OLE DB and ADO tests use TableDump-generated files to identify provider-specific information and to handle provider variations (such as read-only versus read-write, SQL versus non-SQL, and so forth). The TableDump utility generates initialization files needed by the tests. This utility can be found in the \Conformance\Tools subdirectory. For more information about working with the TableDump utility, see Building a Tool (TableDump or Privlib) or Test in this guide.
The MDAC SDK includes some sample test modules in the \Conformance\Tests subdirectory. Each test module is named with an abbreviated form of the interface it tests. These tests can be compiled and run through the Local Test Manager. These test modules are offered only as examples of test code and are not supported in any way. You may not make any claims of conformance based on these tests nor may you redistribute them in whole or in part.
Before you can build any of the OLE DB tests, you must first build the Private Library (Privlib.lib), which is used by these tests.