TFS Build can not support MVC 3.0 and Razor Tests - by louisila

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 665529 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 4/28/2011 1:18:31 PM
Access Restriction Public

Description

TFS is reporting no errors, and build completes, however TFS reports it as a partial completion.

0 error(s), 0 warning(s)
 1 projects/solutions compiled
$/path/blah.sln - 0 error(s), 0 warning(s), View Log File
 1 test run(s) completed - 100% average pass rate (100% total pass rate)
147/147 test(s) passed, 0 failed, 0 inconclusive, View Test Results
 No Code Coverage Results
Visual Basic 4.0, MVC 3.0 Razor, Nuget{autofac, CSLA, Spackle, NSubstitute}, treat warnings as errors : Microsoft All Rules, TFS Build Server runing in server 2008 r2. (we are running  TFS Build Powertools ) both locally and on the server...

When we Dissable Tests we have full success.

<------------------------ Further Info...  ----------------->

When we run locally all tests pass however we get a blue link in the test results(just above test[0] result list item on far left) that says

"Test Run Warning" 

if your running as normal user you will see:

 Warning
 {Date} Warning: conflict during test run deployment: deployment item 'path\blah.dll' directly or indirectly referenced by the test container 'path\blah.tests.dll' cannot be deployed to 'blah.dll' because otherwise the file 'path\blah.dll' would overwrite deployment item 'path\blah.dll' directly or indirectly referenced by path\blah.Tests.dll.

Error {date} Administrative rights are required for the ASP.NET profile diagnostic data adapter to collect data.     ASP.NET Profiler  

Error {date}This adapter will not be used for this test run.  The following error occurred: Administrative rights are required for the ASP.NET profile diagnostic data adapter to collect data.

                ASP.NET Profiler 

If you run as ADMIN you will only see the warning (no errors)

TFS is configured to use a single dedicated Agent (running as {LOCAL_MACHINE}, and dedicated Controller.

there is a post @ Microsoft.Connect pertaining to this which has no viable workaround

After converting to 64-bit, I get the same warning and a new error...

Warning: conflict during test run deployment: deployment item 'c:\path\blah.dll' directly or indirectly referenced by the test container 'c:\path.tests\bin\debug\blah.tests.dll' cannot be deployed to 'blah.dll' because otherwise the file 'c:\path.tests\bin\debug\blah.dll' would overwrite deployment item 'C:\path\blah.dll' directly or indirectly referenced by C:\path.Tests\bin\Debug\blah.Tests.dll.

Error Cannot initialize the ASP.NET project 'ProjectName'.

Exception was thrown: Could not find WebDev.WebServer40.Exe.

 

(included the path names, as i read in a reference somewhere that capitalization can matter for Casinni in diagnostics)

 

 

We can build run and test locally, however we get a cryptic error message (during test run(above)) which upon successful completion can be clicked on in the test results pane(left above the list of successful test runs)

 

On the BuildServer we get:

The MSTestActivity was invoked without a value for Platform or Flavor. The values Any CPU and Debug were used. 

 





Sign in to post a comment.
Posted by Microsoft on 9/20/2011 at 1:21 AM
The issue of incorrect marking of a build due to a test run warning is a valid bug and we have added it to our backlog for next release.

Thanks,
Visual Studio Product Team
Posted by Microsoft on 9/20/2011 at 1:19 AM
Hello,
We analyzed the issue and the following is what we found:
1. On x86 with ASP.Net collector, if running as NetworkService, there is a Test Run error (even though all testcases passed). And this causes the build to be marked failed (if you remove the aspnet collector, the build passes).
There are two work-arounds:
1. Run the build agent as an administrat or
2. Remove ASP.Net profiler data diagnostic adapter from the test settings,

<<

Error {date} Administrative rights are required for the ASP.NET profile diagnostic data adapter to collect data. ASP.NET Profiler Error {date}This adapter will not be used for this test run. The following error occurred: Administrative rights are required for the ASP.NET profile diagnostic data adapter to collect data. ASP.NET Profiler If you run as ADMIN you will only see the warning (no errors) TFS is configured to use a single dedicated Agent (running as {LOCAL_MACHINE}, and dedicated Controller.

>>



2. On x64 with ASP.Net collector, if running as domain user who is an admin, the previous error disappers and everything succeeds. So I am not at all able to repro, the second error thats mentioned when moving to x64 "Cannot initialize the ASP.NET project 'MvcTestDebnugApplication1'. Exception was thrown: Could not find WebDev.WebServer40.Exe. PC1"

Can you attempt to repro again by running as a domain user who is admin on a x64 machine.

I am resolving the issue. Do let us know if the suggestions do not work and there are additional issue for us to investigate.

Thanks,
Visual Studio Product Team
Posted by Macy [MSFT] on 4/29/2011 at 2:49 AM
Thank you for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project or a video to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 4/28/2011 at 2:14 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)