Я пытаюсь настроить решение Visual Studio, которое упрощает:
BDD
Использование SpecFlow http://www.specflow.org/
Как описано на TekPub здесь: http://tekpub.com/view/concepts/5
Я бы хотел :
Чтобы сохранить все ссылки и зависимости под корнем моего решения структура каталогов
Возможность использовать «Тест с NUnit ", команда при щелчке правой кнопкой мыши в моем проекте TestDriven.NET предоставляет.
Я НЕ хочу:
Я действительно хочу:
More detail and what I have already tried:
When you install TestDriven.NET it places its own version of NUnit in a path like:
When you use NuGet to install the latest version of NUnit it places NUnit in a path like:
NuGet automatically adds a reference to \packages\NUnit.2.5.10.11092\lib\nunit.framework.dll for you. That reference is pretty much worthless if you happen to want to easily execute NUnit tests with the TD.Net menu because TD.Net doesn’t actually use the NUnit dll that NuGet just setup for you.
OR
Why am I trying to do this?
I installed NUnit with NuGet so that I could keep the testing framework libs inside of my solution and under source control. I need the ability to reference things like nunit.framework.dll under my solution's path (Solution_root\packages\NUnit.2.5.10.11092) and NOT reference it from (\Program Files (x86)\TestDriven.NET 3\NUnit\2.5).
I already tried the suggestions here:
and it still seems to be launching TestDriven.Net's version of NUnit instead of the one NuGet installs for me.
I also do not want to manually copy over and replace the NUnit files installed by TD.Net as that doesn’t allow for solution-specific dependency files and isolation under source control.