Hi Van, from our side there is no bandwidth to do this change. We all agree that we need to review the overall architecture of the test cases.
Personally I think all the test cases should be executed against an in-memory database such as Derby or others as suggested by Stephen to execute the tests quickly and without requiring an external database installed on the machine. I addition the test suite should have a configuration file that allows to switch from the in-memory database to the database supported by the product. In this way it is possible to verify if the code is actually working with MySQL without slowing down the development activity or the build server. The current situation in not brilliant because we have some tests executed against myFly and others against MySQL. - Would you like to track this issue on the issue tracker ? Otherwise we can add this activity for the next release in the product roadmap in the unscheduled features section (Architecture enhancements) We could add something like this at the end (http://mifos.org/developers/roadmap/product-roadmap): - test cases re-engineering (choice of an in-memory db, decrease the execution time, ....), Regards, Max ----------------------------------------------------- Massimiliano Parlione - http://w4.ibm.com/bluepages/html/[EMAIL PROTECTED] Current Project: https://w3.webahead.ibm.com/w3ki/display/MIFOS/Home Building 6, Innovation Center, Meeting Room 1 IBM Technology Campus Damastown Industrial Estate Mulhuddart Dublin 15 Ireland Phone (external): +35318152394 Extension Number: 512394 IBM International Holdings BV registered in Ireland with number 903924. Registered office: Oldbrook House, 24-32 Pembroke Road, Ballsbridge, Dublin 4 ------------------------------------------------------- "Van Mittal-Henkle" <[EMAIL PROTECTED] To ndation.org> "Stephen Horgan" <[EMAIL PROTECTED]>, Chico 06/03/2008 23:16 Charlesworth/Ireland/Contr/[EMAIL PROTECTED] E cc "Sam Birney" <[EMAIL PROTECTED]>, "Adam Monsen" <[EMAIL PROTECTED]>, Roberto Musso/Ireland/Contr/[EMAIL PROTECTED], Massimiliano Parlione/Ireland/[EMAIL PROTECTED] Subject Mayfly replacements Hi All, I was reviewing the discussion on irc from yesterday about Mayfly, MySQL and HSQLDB. I definitely agree that it would help us to move forward faster if we did not have this dependency. On more than one occasion I have come close to diving in and making this change. One suggestion is that as a first step you might try generalizing the code such that we could plug in MySQL as a replacement for Mayfly in the current tests, since we know will MySQL will work. Of course, this will be slower than an in-memory db, but at least we know that it can be used to unblock us if we run into Mayfly issues. Once the code is general enough to plug in a MySQL replacement, then it should be in a state where a HSQLDB replacement could also be tried. --Van ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
