Hey Patrick,
On 01/09/10 21:26, Patrick Crews wrote:
We have this blueprint:
https://blueprints.launchpad.net/drizzle/+spec/engine-specific-test-suites
It is basically describing the situation as it now stands - engines
contain their own tests within their own plugin directories.
I'm writing to solicit peoples' thoughts on what to do with the
following engine-specific tests that still remain in the main suite
(tests/t):
Below are the engine-specific tests I could find. I can see reasons for
moving them and for keeping some of them in the main suite (for example,
since Innodb is our default engine, we might keep certain tests in main).
I can definitely see moving the heap and myisam tests to their
respective plugin dirs.
Any thoughts are most welcome,
Sounds good to me, I would possibly think about moving InnoDB out to the
plugin (and embedded plugin too?) as I am guessing at some point it may
be possible to compile/run drizzle with just pbxt or something.
Kind Regards
--
Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
