Andy Lester wrote: >> >> [EMAIL PROTECTED]: /home/jpipes/repos/drizzle/testing-overhaul]$ >> sudo make dtest > > Well, you definitely don't want to run dtest as root.
Yes, point taken. > 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. OK, I do not have that installed. Not being a Perl guy, could you give the list instructions on doing that? Thanks! >> 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? Actually, I got that, but was referring to the end of the output: not ok 11 - Server did not shut down after 11 seconds # Failed test 'Server did not shut down after 11 seconds' # in t/run-dtests.t at line 75. 1..11 Is there a testrun log file which has outputted error messages or will all errors go to STDERR? >> 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? Yes, I have code right now that I would like to throw into the test suite. Specifically, the Serialize::TableDefinition class defined in drizzled/serialize/table_definition.h/.cc. Currently, I am running tests on that class using standard printf and assert calls in the drizzled/serialize/test_table_definition.cc file, but would love to move that test into a standard place. >> 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. Sure, but I was hoping not to be the spike-driver on this one :) Remember that not all contributors have a ton of experience. Sometimes all it takes to get the ball rolling is to create easy-to-reproduce instructions and let others run with it. Can you do a step-by-step on the Drizzle wiki when you get a chance? And don't worry, I completely understand everyone's got a day job. There's no time expectations. :) Cheers, Jay > It > will probably be an automated process we need only do once, unless it > relies on something we don't handle, like master/slave. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
