[EMAIL PROTECTED]: /home/jpipes/repos/drizzle/testing-
overhaul]$
sudo make dtest
Well, you definitely don't want to run dtest as root.
I'm looking to see if I've somehow not pushed some makefile.am changes.
In the meantime, all "make dtest" does is "prove t/". Make sure you
have Perl with Test::Harness 3.00 or higher installed.
Cool, that worked, but produced a failure:
/home/jpipes/repos/drizzle/testing-overhaul/client/.libs/lt-
drizzleadmin:
unknown variable 'socket=/var/run/mysqld/mysqld.sock'
How do I see what the error was?
Looks like it was trying to start up the daemon incorrectly, no?
No problem. But, I do have some questions about the current format.
How can I use this testing framework to test other things, like the
connectors, the APIs, C++ code? Right now, it just seems to handle
the
results of a query as displayed by the drizzle client?
Right. When we need those other things, we'll deal with them.
handle tests that I write for C++ code, what do I need to do? Do I
write the test in C++? Your advise is welcome :)
Do you have actual C++ code right now, or are you just talking in
general?
on, for instance, breaking things into many smaller tests instead of
fewer large tests. How can I help in this regard? Shall I create
some
blueprints to get the process rolling?
Drive a spike. Pick a .test/.result pair and convert it to .dtest
format. From there, we can document how we're going to do that. It
will probably be an automated process we need only do once, unless it
relies on something we don't handle, like master/slave.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
