Yes, making some type of change would be helpful. Ironically, I've always had trouble running the tests, since I have neither Oracle or MS SQL setup here. Just MySQL.
Ideally, we should be able to run the tests for whatever databases may be available to a developer, by loading multiple configurations, if need be. It could also turn into a working example of using multiple database providers in the same application. (This is something that we could also discuss on ibatis-dev@, since it involves changing the codebase, rather than just using it. If someone wants to move the thread, that's OK with me.) -Ted. On Wed, 22 Dec 2004 23:15:34 -0500, roberto wrote: > Could we change the Init() structure to accommodate running > different SQL scripts depending on the database being tested? > > I’ve resorted to separating out the various Oracle statements into > their own SQL files and modifying the Init() methods of the current > tests. I briefly toyed with the idea of using EXECUTE IMMEDIATE > and reworking the ScriptRunner to use an Oracle package with ref > cursors to run the DDL statements in one script/command text but > quickly got over it! > > Anyway, I think the project may already have been headed in this > direction given the MSSQL tests in their own namespace. > > For example: > > Make NUnit.SqlMapTests.StatementTest abstract. Create an > NUnit.SqlMapTests.Oracle namespace (like the existing MSSQL > namespace). And create an NUnit.SqlMapTests.Oracle.StatementTest > with a different Init(). > > Additionally, we can tag the specific db tests by NUnit Category > such as [Category(“MSSQL”)], [Category(“MySQL”)], and > [Category(“Oracle”)] or use some other convention. > > Roberto
