1. Always consider Environment.CurrentDirectory as opposed to Assembly.GetExecutingAssembly().Location, when getting current working directory.
This innocent looking line of code causes grief.
var pathToSqliteDatabase = Path.Combine(Assembly.GetExecutingAssembly().Location, "SqliteDb.db3");
Let’s just first ignore the fact that a test harness should be going directly to a database since this is part of the problem. But if you are running a test harness that has to resolve a location to an SQLite database instance you will get interesting results.
If using MSTest, the above line of code resolves to the current test project’s working folder. So if your test project was in c:\dev\SQliteAdventures, pathToSqliteDatabase to be
However, if you decided to change to NUnit and have ReShaper installed, the same above line of code now resolves to some random location:
In my case, it looked like this:
Changing the above line of code to
var pathToSqliteDatabase = Path.Combine(Environment.CurrentDirectory, "SqliteDb.db3");
will return the current result regardless of the operating environment. So this is preferable here.
2. Carefully consider using x86 vs x64 versions of 3rd party dependencies.
The System.Data.SQLite.dll .NET connector for SQLite, for example comes, with an x86 and x64 version. When executing tests using MSTest, x86 version of the is required since the MStest runner executes within the 32 bit Visual Studio process. However, if you are running NUnit via ReSharper, which executes within its own 64 bit process called JetBrains.ReSharper.TaskRunner.CLR45.x64.exe, you need the x64 bit version of this dll otherwise you get image loading exception. Besides testing against abstractions or fakes, I do not yet know to automate this. Ideas always welcomed.
To be continued…..