StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
695674
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-30T00:14:33.247
FavoriteCount
0
LastActivityDate
2009-03-30T00:14:33.247
LastEditDate
LastEditorUserId
0
OwnerUserId
84369
ParentId
616488
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>VS essentially offers this ability for free by generating the TRX file to summarize the results of a test run. There are a number of different ways to run all tests in a project but pick one and off mstest will go running each method with the [TestMethod] attribute and producing a UnitTestResult in the results file. </p> <p>What you're asking for is essentially what the Test Results window shows you after a completed Test Run. If you're looking for something external to VS, you could always run a simple XSLT transform against the Test Results (.trx) file giving you a customized summary. Here's a very rough sample which proofs the concept, generating an HTML document containing an unordered list with a list item (test name and result) for each unit test:</p> <pre><code><?xml version='1.0'?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:vs="http://microsoft.com/schemas/VisualStudio/TeamTest/2006"> <xsl:template match="/"> <html> <head> <style type="text/css"> body { font-family: verdana; font-size: 12px; } .pass { color: green; } .nopass { color: red; } h1 { font-size: 13px; margin: 3px; } ul { margin: 3px 20px 3px 40px; } </style> </head> <body> <h1>Test Results</h1> <ul> <xsl:apply-templates select="//vs:Results//vs:UnitTestResult" /> </ul> </body> </html> </xsl:template> <xsl:template match="vs:UnitTestResult" > <li> <xsl:value-of select="@testName" /> &#160; <xsl:variable name="Result"> <xsl:choose> <xsl:when test="@outcome='Passed'">pass</xsl:when> <xsl:otherwise>nopass</xsl:otherwise> </xsl:choose> </xsl:variable> <b class="{$Result}"> <xsl:value-of select="@outcome" /> </b> </li> </xsl:template> </xsl:stylesheet> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMSTEST/VSTS Reflection Tool
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJohn Lewin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMSTEST/VSTS Reflection Tool
  singulars
  PostTypePostTypeId
  PTQuestion
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
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
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.