Hi everyone, 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, Patrick tests/t - engine tests: heap_auto_increment.test heap_btree.test heap_hash.test heap.test heap_var.test index_merge_myisam.test mix2_myisam.test myisam-blob.test deadlock_innodb.test index_merge_innodb.test innodb-semi-consistent.test join_outer_innodb.test rowid_order_innodb.test unsafe_binlog_innodb.test func_group_innodb.test innodb_mysql.test innodb.test loaddata_autocom_innodb.test subselect_innodb.test group_min_max_innodb.test innodb_notembedded.test innodb_trx_weight.test parser_bug21114_innodb.test
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
