Freitag, 9. März 2012 09:18
we've got multiple projects and multiple unit test projects. Some of them need to be hosted on asp.net dev server. Others don't need to be hosted there.
The big problem is, that I've only 1 Testsetting-File which I've to configure running on asp.net. Also for the tests that don't need this host. So is it possible to use different testsettings on different test-projects? Would be really cool and a very very fine performance boost for our testing. Waiting until the webserver is startet really hurts each time!
I couldn't find any configuration how to solve this issue. Probably there is an other possibility to avoid starting the webserver all the time when I run a test even if this test doesn't need it.
Freitag, 9. März 2012 12:02
You can create multiple test settings in a solution. See Create Test Settings to Run Automated Tests from Visual Studio.
You won't be able to set separate test settings project wise, but you can set/change one of the available test settings as active. See How to: Apply Test Settings from Microsoft Visual Studio.
So, you can set the required test setting as active as per your requirement before execution.
Montag, 12. März 2012 07:42
thats what I found on the web too. I thought probably there is a workaround. Probably @the next versions...