Testing Your Provider
Before you release a provider, you should do the following tests, in the order indicated. These tests show that the provider functions properly for most potential users.
Test the provider using a consumer application written with the OLE DB consumer templates. The test consumer should cover all functional areas of your provider (all code that you've added or modified).
Test the provider using a consumer application written with ADO. Most developers (especially Microsoft Visual Basic and Microsoft C# developers) use ADO or ADO.NET for consumer applications. The test consumer should cover all functional areas of your provider. For an example of an ADO consumer application, see ADO Code Examples in Microsoft Visual Basic.
Run the OLE DB conformance tests (including ADO conformance tests) to show that your provider meets the level 0 standard for OLE DB providers. (For an explanation of level 0, search for OLE DB Level 0 Conformance Tests at OLE DB Programmer's Guide. These tests and associated documentation are included with Visual C++ in the Data Access SDK. These tests also help to show that your provider runs well when aggregated by other service providers and are especially useful if you modify or add properties. For more information about the conformance tests, see the Readme file for the Data Access SDK, which is located on one of the Visual Studio CDs.
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for