Difference between revisions of "Database/Drivers/MySQL Native/TestingIdeas"
(→Ideas for testing Connector/C++ and Connector/OpenOffice) |
(→UNO) |
||
| Line 17: | Line 17: | ||
=== UNO === | === UNO === | ||
| − | We could use UNO to run the Java/JDBC tests against the C++ based Connector/OpenOffice. | + | We could use UNO to run the Java/JDBC tests against the C++ based Connector/OpenOffice. |
| + | |||
| + | This might require a running OOo in the background. | ||
=== Manual conversion of JDBC tests into C++ === | === Manual conversion of JDBC tests into C++ === | ||
Revision as of 14:54, 6 May 2008
Contents
Ideas for testing Connector/C++ and Connector/OpenOffice.org
This is brainstorming, no more.
We have a rich set of JDBC tests but only few SDBC and dedicated Connector/C++ tests. SDBC is based on JDBC 1.0 and Connector/C++ will support even higher versions of JDBC. Thus it seems interesting to use the MySQL Connector/J (JDBC) tests - its 100k loc of unit tests.
Recall that on the long run Connector/OpenOffice.org will be a wrapper of Connector/C++. Finding ways to test Connector/C++ means finding ways to test at least parts of Connector/OpenOffice.org
JDBC2SDBC wrapper
Ocke has developed a JDBC2SDBC wrapper.
JNI
We could run the JDBC tests using JNI and load Connector/C++ as an external library into Java.
UNO
We could use UNO to run the Java/JDBC tests against the C++ based Connector/OpenOffice.
This might require a running OOo in the background.
Manual conversion of JDBC tests into C++
Given that we need to convert 100k loc, its unlikely that this can be accomplished in a timely manner in order to achieve continous integration testing.
(Semi-)Automatic conversion of JDBC tests into C++
Develop a conversion tool which handles the most basic and time consuming conversions.
