Jasmine in a separate test project

Traditionally, I've always kept unit tests in separate assemblies.

I've read both sides of the argument and prefer not to ship code that isn't production code, or to have additional deployment steps to remove tests from production code.

In order to reference javascript in my Web.Client.Tests assembly, for example, I use a post-build event to copy the files into the test project. For this I use robocopy - it looks something like this:

robocopy "$(ProjectDir)app" "$(SolutionDir)Tests\Presentation\Web.Client.Tests\app" /E /COPY:D /IS 

robocopy "$(ProjectDir)Scripts" "$(SolutionDir)Tests\Presentation\Web.Client.Tests\Scripts" /E /COPY:D /IS

if errorlevel 1 GOTO :eof 

The main con with this approach is that you have to build the project each time, like you'd have to with your C# code, to update the test project before running the tests.

You can do this with no copy/pasting. In your Jasmine tests you can add a /// <reference comment which posts to your source files (or the directory containing them). For example given this sturcture

/ProjectA /scripts

code1.js
code2.js

/TestProjectB test1.js

You can add this line at the top of your test1.js file to reference all your code files:

/// <reference path="../scripts" />