All geek questions in one place

What are the best methods for the AspNetDevelopmentServerHost attribute?

We have a web application project (actually actually ...) that comes with a testing project. In a test project, I have a simple unit test that executes several methods.

Runs locally, runs a unit test, and works.

However, when our TFS Build server tries to run the test, it fails with an error regarding the invalid path for the AspNetDevelopmentServerHost attribute. Other team members can do this as best as possible.

The problem is that the root of my TFS workspace is set to c: \ projects \ One of the team members is set to c: \ tfs2008 \ The TFS build server, on the other hand, sets the pathToWebRoot variable to "c: \ blahblah \ Release_PublishedWebsites ... "This leads to the wrong way.

Due to the number of projects that we have, I cannot have everyone reset the environment variable every time I switch projects.

So, what are the best practices for web projects for unit testing in a team environment? The MSDN article turned out to be less effective than useful.

+3
source share
3 answers

%pathtowebroot%\\WebSiteName pathToWebApp AspNetDevelopmentServer AspNetDevelopmentServerHost.

+3

:

<TestMethod(), _
 HostType("ASP.NET"), _
 AspNetDevelopmentServerHost("$(SolutionDir)\\MyWebProject", "/"), _
 UrlToTest("http://localhost:44444/")>
 Public Sub Test()
     AssertStuff();
 End Sub

$(SolutionDir) , , . , , , .

+3

You can set environment variables during build to change the path and still work in the local environment.

+1
source

Source: https://habr.com/ru/post/1709527/

More articles:


All Articles