VSTS Testing for ASP.NET still isn't where it should be

After my last post on the subject, I'm sorry to say that I'm no better off than I was before. Unfortunately, debugging tests in ASP.NET simply doesn't work, and there's no good excuse for it.

Now I ask you, how is it that the team developing the testing framework for VS was allowed to ship the tool without it doing what it's supposed to do? These kinds of head scratchers drive me crazy in the face of what I'd consider brilliance otherwise. I just don't get it.

To recap, as indicated in this useless article, you can't debug because VS isn't smart enough to attach itself to the process it's creating to run the tests.


Trying harder to attach to the dev server process, I discovered that it creates a new instance when you run the tests, which is not what is described in the above linked article. My test attributes look like this:

[AspNetDevelopmentServerHost("%PathToWebRoot%\\PopForums.Test.Web", "/PopForums.Test.Web")]

1 Comment

Comments have been disabled for this content.