Hi Christoph,
Christoph Neumann escribió:
Hi Ariel,
Ariel Constenla-Haile wrote:
Hello Christoph,
finally I set up (almost) everything (I still have to set up the env.
to test database related cases), and could make it work.
I took the list of missing *component* test cases for
"http://qa.openoffice.org/qadevOOo_doc/missing.html";, created an
scenario with all of them (I send you the file sce attached),and run the
Runner (sorry for the redundancy):
* first result: this list very old, because every component but one
has its test case
Oh dear! Yes, this list is _very_ old. Maybe I can update this list next
week.
* there where two errors: mod._toolkit.AccessiblePopupMenu and
mod._odbc.Driver
Concerning this last one, the log (I send you a copy) says:
***** State for odbc.Driver ******
Couldn't find mod._odbc.Driver java.lang.ClassNotFoundException:
mod._odbc.Driver
Whole component: Couldn't find mod._odbc.Driver
java.lang.ClassNotFoundException: mod._odbc.Driver
So this the only missing component test case in the list.
I can't see very clearly the difference between odbc.ODBCDriver and
odbc.Driver. My guessing by reading the qadevOOo/objdsc/odbc/
* com.sun.star.comp.sdbc.ODBCDriver.csv is the object description for
the object implementation odbc.ODBCDriver , this one has a test case
(mod._odbc.ODBCDriver). Is this the implementation of the *generic* ODBC
driver?
Yes, it is.
* for the name of the oder objdesc
org.openoffice.comp.drivers.MySQL.Driver.csv, I guess this is the
implementation of the *MySQL* *dediacted* ODBC driver, isn't it?
MySQL-Driver is a wrapper around ODBCDriver. This driver works around
some MySQL bugs. Additionally it has some helper interfaces.
If so, the test case for odbc.Driver won't be very different from the
one for odbc.ODBCDriver: the difference will be when creating the
environment we should try to get the parameter "mysql.url" from the
runner.props, and check that is "sdbc:mysql:odbc" instead of
"sdbc:mysql:jdbc". Am I wrong?
No, I think you are right here. The parameter "mysql.url" seems to be
the way to go.
Today I will set up my database environment so I can give it a try.
Please let me know if you have an up-to-date list of missing Java test
cases for components and interfaces.
As I said before I will try to update this list next week. Maybe it's
better to have a wiki page for this purpose.
good idea . By the way, the wiki about getting the sources through
NetBeans CVS implementation was very useful (I will try to take some
screen shots of the step-by-step to add to the wiki)
And if you want to give me a first task to begin with, I think I'm
ready :-)
Well, you have to be able to commit source into the cvs or I have to be
allowed to use your patches/ new written tests. Therefor you have to
agree to the "Joint Copyright Agreement":
See: http://contributing.openoffice.org/programming.html
and:
http://website.openoffice.org/files/documents/28/1006/contributing.html
I'll read this today and let you know
This enables me to commit your patches into the cvs at first. I think
this is they way we should start to handle your code. If you have
finished the TestCase for MySQL you can write an Issue:
I will try to set up the unixODBC today (sounds like a shame, but I
never used it -- I always tend to use JDBC )
Component/Project: API
Subcomponent: code
IssueType: Task
Assign to: [EMAIL PROTECTED]
Summary: runner: odbc.Driver
Please attach your code then.
And if you like you can try to fix
http://www.openoffice.org/issues/show_bug.cgi?id=71085
I'll check that :-)
This is also a database related issue.
If you have further questions don't hesitate...
Greetings,
Christoph
Regards,
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
