The name ‘DatabaseFixtureSetup’ does not exist in the current context
Everything seemed ok prior to inheriting from Microdesk.Utility.UnitTest.DatabaseUnitTestBase, but I could be wrong.
Any ideas?

Thanks for the positive feedback; I’m glad to hear that you were able to get value out of the content.

Could you either post the code (of the test that’s throwing the exception) or ZIP the whole thing up and e-mail to me (sbohlen AT gmail.com) so I can take a look at it for you?

-Steve B.

I listend through the summer of nHibernat section of yours and I am extremely impress by the content that you have put together for all of us. I really appreciate and thanks for all the hard work that you have done. This is the best tutorials set that I have ever seen.

I have a question regardng Microdesk.Utility.UnitTest. I am new to ndbunit and nhibernate so please forgive me for asking me dumb questions.

After reading some of your postings and documentations, I realise tat ndbunit does not support oracle yet. But in this post, you have mentioned in this post that

” Even though the MS OleDB provider is almost never as ‘fast’, ‘efficient’, or ‘capable’ as using the DB vendor’s ‘native’ windows driver, for the very simple CRUD work that NDbUnit needs to perform its almost alway at least *workable*. ”

So I tried connecting Oracle with OLEDB Provider while estabishing the Database.xsd file. But when my test runs and when it calls DatabaseFixtureSetUp() method, I get the following error message. I am not sure if I understand this post correctly or doing something wrong.

Could you provide some light to this problem? Thanks in advance.

TestCase ‘M:NdbUnitOledbProviderTest.NdbOracleSupportTests._TestFixtureSetup’ failed: Keyword not supported: ‘provider’.
System.ArgumentException: Keyword not supported: ‘provider’.
at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey)
at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules)
at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous)
at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(String connectionString, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
at System.Data.SqlClient.SqlConnection.ConnectionString_Set(String value)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at System.Data.SqlClient.SqlConnection..ctor(String connectionString)
at Microdesk.Utility.UnitTest.DatabaseUnitTestBase.ValidateSchemaAgainstDatabase(String schemaFilename)
at Microdesk.Utility.UnitTest.DatabaseUnitTestBase.DatabaseFixtureSetUp(Boolean ignoreSchemaDifferences)
at Microdesk.Utility.UnitTest.DatabaseUnitTestBase.DatabaseFixtureSetUp()
C:\Source\NHibernate\TUTORIALS\Summer of Nhibernate Session 14 Code\NdbUnitOledbProviderTest\NdbOracleSupportTests.cs(24,0): at NdbUnitOledbProviderTest.NdbOracleSupportTests._TestFixtureSetup()

I have a small question concerning DB Persistance using mbUnit with your really cool UnitTest library !

I have a table with a column type timestamp.

When the insert are launched for a resync after a test this error occurs :

“… CANNOT INSERT EXPLICIT VALUE INTO TIMESTAMP …”
I tried to removed the timestamp field from the xsd schema, but after I have errors telling me that a parameters is missing.

How do you handle this column type with mbUnit ?

Tx you for you help ! And tx you for you websites !!!

SeeMe

Oracle Support is still in progress; the release of the version 1.3.0 code was actually to accommodate the inclusion of patches that I rec’d unexpectedly that introduced support for SQLLite and SQLCe.

I wanted to fold these patches into the trunk ASAP and make them available for others ASAP so I did this release with support for these DB targets even though the roadmap claimed Oracle support was supposed to be ‘next’.

With some luck, I will have Oracle support completed soon (unless someone else submits a patch to me that provides it first, in which case I will have Oracle support completed sooner )

I’d like to use NDbUnit but am running an Oracle database.

Thanks!

Yes, my utility basically sits on top of the NDbUnit library and merely provides convenience automation methods for its own internal methods. NDbUnit doesn’t presently support Oracle as a database target and so I don’t doubt that it isn’t working for you against Oracle.

The good news however is that I am actually also presently in charge of the NDbUnit project ( http://code.google.com/p/ndbunit ) and I am in the process of integrating a patch submitted by someone that introduces Oracle support to the library.

Once this is complete (probably another two weeks or so given other demands on my time) I will release an update to NDbUnit and a corresponding update to my own utility that works along with it properly.

So the good news = its in the works but the bad news = what you are attempting right now is essentially unsupported.

HTH,

-Steve B.

Thanks
Jean