I know this has previously been talked about and some people were opposed to
use in memory sql lite db to run the database unittests. (sorry can't find the
link to that discussion).
At the moment the major reason why we only have 2 working TeamCity agents is
because we require a physical SQL server to run the tests, and it gets worse!
Because we are passing parameters on the TC build scripts eg:
-D:ar.dialect=NHibernate.Dialect.MySQL5Dialect
-D:ar.connection.driver_class=NHibernate.Driver.MySqlDataDriver
-D:ar.connection.connection_string.1="server=myserver;User
ID=***;Password=***;database=castle_test1;"
-D:ar.connection.connection_string.2="server=myserver;User
ID=***;Password=***;database=castle_test2;"
-D:ar.query.factory_class=NHibernate.Hql.Classic.ClassicQueryTranslatorFactory
we are restricting other agents from being able to chose their own database
server, database names, UserId, and password.
Another problem is for users that want to run the tests local on their own
workstations, to do this they have to pass this massive arguments list to nant.
Has anyone had success running all the db tests using SQLLite?
Should we aim to change all the db tests to run against SQLLite, and as part
of that get rid of all these parameters?
Cheers
John
__________________________________________________________________________________
Yahoo!7: Catch-up on your favourite Channel 7 TV shows easily, legally, and for
free at PLUS7. www.tv.yahoo.com.au/plus7
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
