When I first started out with VSTS I created a nightly build project. Since I was just setting up my solution I did not yet have any tests to run.

Team Build unfortunately is a one way interface.  Once you setup the build the only editing experience you get in MSBuild!

So the trick to adding tests to a build without them is as follows.  Look for:

    <TestingFlag>false</TestingFlag>
    <!--  TEST ARGUMENTS
          If the TestingFlag is set to true then the following is relevant
          Metadatatest file path - mandatory
          Testlist name, a test list which is a part of the selected metadata file - mandatory
          Runconfiguration file path - optional, defaults to the active run configuration in the metadatafilename
        
    -->
    <TestingArgs> </TestingArgs>

Change the TestingFlag to true and point it at the vsmdi file in your solution which contains information about which tests to run.  Like this:

    <TestingFlag>true</TestingFlag>
    <!--  TEST ARGUMENTS
          If the TestingFlag is set to true then the following is relevant
          Metadatatest file path - mandatory
          Testlist name, a test list which is a part of the selected metadata file - mandatory
          Runconfiguration file path - optional, defaults to the active run configuration in the metadatafilename
        
    -->
    <TestingArgs>/testmetadata:$(SolutionRoot)\VergentSoftware.SeattleTraffic.vsmdi</TestingArgs>

Thursday, May 19, 2005 8:35:23 AM (Pacific Standard Time, UTC-08:00)         Comments [0]   VSTS