Have a look into dbunit: http://dbunit.sourceforge.net
We have similar issues with classes relying on stuff from a database and we dynamically pick a different implementation to point at data access object implementations picking up dummy data You should also define a TestSuite and pass it into your CI system to only run those testcases that can be run automatically instead of simply running every test case inside your test directory. -j --------------------------------------------------- Justin Fung [EMAIL PROTECTED] Sr. Analyst, Business Systems IT Banking Systems, e-Business HSBC Bank Canada http://www.hsbc.ca p: (604) 643-6605 f: (604) 643-6727 Kris Nuttycombe <[EMAIL PROTECTED]> 05/19/2006 10:08 AM Please respond to "Maven Users List" To: Maven Users List <users@maven.apache.org> cc: Subject: Best practices question - junit/database/m2/continuum Our Ref: Your Ref: Hi, all, Here's my problem: much of the code that is written in my organization makes extensive use of vendor-specific database features (such as spatial data types, etc.) In order to unit test our code, we obviously need to be able to configure the database connection information, which we are doing using filtering such that each developer has a locally configured filter file that is not checked in to subversion. The problem arises when running the tests using continuum - since we don't want to check the connection information into source control (which we may want to have externally visible), it's not available when continuum checks out the project. Is there any set of best practices for how to deal with this issue? Since we're using vendor-specific features, we cannot use an in-memory database for the tests, as I would have preferred. Thanks, Kris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *************************************************************** This email may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email by anyone other than the named recipient is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. Internet email is not private, secure, or reliable. No member of the HSBC Group is liable for any errors or omissions in the content or transmission of this email. Any opinions contained in this email are solely those of the author and, unless clearly indicated otherwise in writing, are not endorsed by any member of the HSBC Group. *************************************************************** Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel par toute personne autre que le destinataire désigné est interdite. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. La transmission de courriel par Internet ne constitue pas un mode de transmission confidentiel, sécuritaire ou fiable. Aucun membre du Groupe HSBC ne sera responsable des erreurs ou des omissions relatives au contenu ou à la transmission de ce courriel. L'auteur de ce courriel est seul responsable des opinions émises dans ce courriel, lesquelles, à moins d'un avis contraire fourni par écrit, ne sont pas endossées par aucun membre du Groupe HSBC. ***************************************************************
