StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3623326
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-02T01:53:46.740
FavoriteCount
0
LastActivityDate
2010-09-02T01:53:46.740
LastEditDate
LastEditorUserId
0
OwnerUserId
282326
ParentId
3615322
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I find a three step elimination is useful: <ol> <li>Do the tests run in Visual Studio dev environment?</li> <li>Do the tests run in msbuild locally?</li> <li>Do the tests run in msbuild on the build server?</li> </ol> I use the build.cmd script below to run msbuild on my local machine in an environment that very closely matches what will be used by the TFS build server. <h2>build.cmd script</h2> <pre><code>@setlocal SET MSBUILDVER=v4.0.30319 SET MSBUILDEXE=%FrameworkDir%%MSBUILDVER%\MSBuild.exe SET builduri=local %MSBUILDEXE% BuildDefinitions\TFSBuild.proj %* </code></pre> NOTE: This script must be run from a Visual Studio 2010 command prompt window: Start -> All Programs -> Microsoft Visual Studio 2010 -> Visual Studio Tools -> Visual Studio Command Prompt (2010) In general, setting the true in TFSBuild.proj should cause unit tests to run automatically in any solutions listed in the build, but it sounds like that is not working for you? What happens if you pass command line option /p:RunTest=true to msbuild from command shell? You should be able to add custom TFS build command line options to the server build through the TFSBuild.rsp file if necessary, but should not really be necessary for RunTest. TFS build server should automatically create a .trx results file -- check the build results through Build Explorer in Visual Studio -- the View Test Results will open the .trx file in VS. Not sure about solutions to your other specific problems, but i would try running the build in a command window locally to get a clearer view of what is happening during the build. Error messages will show up as red text, warning messages as yellow text, and lots of other intermediate build step info as grey text. There are lots of good blog posts around about TFS build subjects -- Aaron Hallberg's blog (blogs.msdn.com/b/aaronhallberg) would be a good place to start. Also, MSDN has lots of good info on TFS / MS Build - for example: <a href="http://msdn.microsoft.com/en-us/library/ms181721(v=VS.90).aspx" rel="nofollow noreferrer">Running Builds in Team Foundation Build </a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORunning MSTest Unit tests As part of TeamBuild
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJorgen Thelin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.