Unit Tests No Longer Run on Build Server

[Steve Barker]

Hi all,

I'm having a weird problem with my auto-build on the build server. I have
configured continuous builds, and so far this has been working perfectly.
However, for some reason the unit tests have stopped running automatically
and I can't tell why.

I don't even know where to start looking! Under the section entitled "Result
details for Any CPU/Release" it just says “Test Results: No test result” and
“Code coverage result: No coverage result”. The build definition is
configured to include tests in two lists, and I’ve used a test container.
This has always worked in the past. We now have 909 tests in one test list,
but surely this wouldn’t cause a problem?

Thanks,

Steve.

[Hongye Sun [MSFT]]

Hi Steve,

Thanks for your post.

This looks like a configuration issue, however the information here is
limited. Can you follow the action plan as below to narrow down the issue
quickly?

1. Create a new build definition
The new definition should build the same projects and run the test list or
test container, and try to run it.

2. Check change history on build project file
The file should be located at
$<Root>\TeamBuildTypes\<ProjectBuild>\TFSBuild.proj. Please check the
changes between the time of last successful build and first error build.
Make sure that the following configuration sections are set correctly:
<RunTest>true</RunTest>
<TestContainer Include="Path of DLLs" />
<RunConfigFiles>Path of testrunconfig file</RunConfigFile>

3. Send me following files

1) TFSBuild.proj file

2) TFS build log file, which is located at build folders and its name is
BuildLog.txt.
Please also send me the old build log file which logs tests are
successfully run.

3) The testrunconfig file

My email address is ***@online.microsoft.com, remove 'online.'
Once I get your reply or email, I will analyze and response to you at my
first time.

Please also let me know if you have anything unclear. Thanks.

Regards,
Hongye Sun (***@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
***@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within?2 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Steve Barker]

Hi Hongye,

It's still not working, so I'll send you the files you requested...

Cheers,

Steve.

Post by Steve Barker
Hi all,
I'm having a weird problem with my auto-build on the build server. I have
configured continuous builds, and so far this has been working perfectly.
However, for some reason the unit tests have stopped running automatically
and I can't tell why.
I don't even know where to start looking! Under the section entitled "Result
details for Any CPU/Release" it just says “Test Results: No test result” and
“Code coverage result: No coverage result”. The build definition is
configured to include tests in two lists, and I’ve used a test container.
This has always worked in the past. We now have 909 tests in one test list,
but surely this wouldn’t cause a problem?
Thanks,
Steve.