Short, short version (for those with no time):
I have Sqlite tests ~passing. SqlServer isn't passing, apparently
because SqlServer express isn't configured properly. Any directions on
what to do to set up a SqlServer express database for testing?
On Tue, 2009-03-03 at 20:14 +0100, Pascal Craponne wrote:
> The NUnit project is the DbLinq.nunit file, in tests/Test_NUnit
> folder. It works fine, since I use it to generate the reports on the
> wiki.
>
Sometimes[0], I swear computers hate me.
So in this case, I built dblinq trunk using the DbLinq.sln file
(ignoring all the warnings that Express threw up on load).
I went to the tests/Test_NUnit directory and opened DbLinq.nunit within
NUnit. It promptly failed during load, saying that it couldn't load
Test_NUnit_SQLite or one of its dependencies. The file does exist.
Start FUSLOGVW.EXE (the Fusion Log Viewer), enable logging, re-try, and
see errors appear for nunit.core.interfaces, nunit.core,
nunit.core.extensions, and Test_NUnit_SQLite. Go crazy, as the first
two and the last assembly exist within the tests/Test_NUnit/bin
directory.
Get slightly puzzled as the Fusion log indicates it's searching for
version 2.4.8, while the nunit.* assemblies within lib and
tests/Test_NUnit/bin are 2.4.7. Perhaps this is the problem?
Give up on the DbLinq.nunit file, go to the tests/Test_NUnit/bin
directory within Explorer, load Test_NUnit_SQLite.dll within NUnit, and
run. Success!
Well, not entirely; 430 tests found, 413 run, and 149 failed. But at
least most passed. (Enough to give me confidence that something is
working properly.)
Does this jibe with anyone else?
Go back to my branch, where DbLinq.Sqlite_test fails everything, and
investigate. Find that the TestBase.connStr property reads a
ConnectionStrings.xml file, and since I'm now placing the NUnit tests
into the build directory, the path to find ConnectionStrings.xml is now
wrong. Fix. Read ConnectionStrings.xml, and find that it uses the
assembly name...which I've been changing. Fix.
So for those still with me, I'm now able to run DbLinq.Sqlite_test.dll
and get the same pass/fail result as trunk. Yay.
Move on to Test_NUnit_MsSql.dll, and see more fail:
Test_NUnit_MsSql.WriteTestSetup (TestFixtureSetUp):
System.Data.SqlClient.SqlException : A network-related or
instance-specific error occurred while establishing a connection
to SQL Server. The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is
configured to allow remote connections. (provider: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance
Specified)
So, that's where the branch currently is: DbLinq.Sqlite_test.dll works
(-ish), while DbLinq.SqlServer_test.dll fails (for the same reason that
trunk's Test_NUnit_MsSql.dll fails -- the database isn't configured).
How do I set up/configure a database for the SqlServer tests?
Of course, to test the other providers (Ingres, Postgre, etc.) I'll need
a way to test them...unless someone who already has the database set up
would like to graciously run the unit tests for me. :-)
- Jon
[0] Every day.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" 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/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
