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]
