Developer Edition and Builds

Hello !

When I read the posts, it seems that we can run tests in a build only with Tester Edition. However, when I ran by build on the server, here is the mesage I got : "MSBUILD : warning : Visual Studio Team System for Software Testers or Visual Studio Team System for Software Developers is required to run tests as part of a Team Build."

So I installed Developers Edition and no more complain. However, no test is executed and this is apparently because no one is defined in my test list. And of course, because I cannot edit my test list in DE.

With the Team Suite (trial edition) I had before, I could configure my build to run all the tests, even the tests not defined in a test list. But this configuration doesn't launch anything now.

My question is : Is there a way to do that or not

I have read also that MS was saying that they will give the ability to edit Test Lists in DE in the next release. So second question : When this new release will be released and can I continue using the Trial Edition in the meanwhile (of course, my 180days are almost over and I don't want to format my computers to reinstall...)

Thanks !




Answer this question

Developer Edition and Builds

  • Andrew Lloyd

    Just wanted to pass along another bit of information regarding the version of VS used on the Build machine.

    You aren't required to have VS for Testers on the build box if you have VS for Developers. The tests will run with either verison installed. The problem is that you cannot create or manage your test metadata (.vsmdi) using VS for Developers, only VS for Testers or VS Team Suite.

    What I have done is place VS for Testers on a test machine, when I need to manage the tests for my Continuous Integratoin builds, I grab all of the solutions that I am building from within the VS for Testers copy. I then create a new test group called "All" and move all of my tests into it and check the while thing back into Version Control. Now my build can run the tests by setting "RunTests" to true in TFSBuild.proj.

    It's a bit of a pain to have to use a standalone VS for Testers on another machine (btw, you can run both version on the same PC if you like) just to manage the vsmdi files, but my company is not purchasing Team Suite for all of us...

    If you have any questions about how we are managing it, please feel free to drop me an email at: stevREMOVETHISen.st.jean@fmREMOVETHISglobal.com

    -Steve



  • Cleverp

    Sorry I don't know. What I have read is that you need to install the testing tools to be able to run test on the TFS server. So to do that, I have installed the testing tools from the Developper Edition (which is already a subset of the Developper Edition). Don't think you can install only a subset of that. Maybe a MS guy can confirm that.

  • Natallica

    Is there a way to install MSTest only and not the rest of the components We have the team build server edition and we prefer not to install the whole developer edtion.

    Thanks


  • Coriolan

    Ok found a solution :

    Stop me if I'm wrong but here is the solution I'm now puitting in place

    • Stop using tests lists (pity)
    • Update your "proj" file to
      • not run test during the builds
      • Run a new task (I'm doing in the AfterCompile target) which will
        • Run manually you tests
        • Publish the test results to the server

    See the task I'm using :

    <Exec Command="$(ExecutionTest)" />

    with the variable:

    <ExecutionTest>"C:\program files\Microsoft Visual Studio 8\Common7\IDE\mstest.exe" /testcontainer:"$(BinariesRoot)\Mixedp~1\Release\MyTestDll.dll" /runconfig:"$(BinariesRoot)\..\Sources\MySolution\TestRunConfig1.testrunconfig" /publish:MyServerName /publishbuild:"$(BuildNumber)" /teamproject:DH2 /platform:"Mixed Platforms" /flavor:"Release"</ExecutionTest>

    I can add a line for each test DLL I have in my solution



  • Joe Bruce

    Hey Jarod,

    I hope you still keep track of this thread. We want to run some tests without the VS tester edition. But our build server doesn't have MSTest.exe. So we tried to write a condtion command as the following:

    <Target Name="AfterCompile">

    <Exec Command="$(ExecutionTest)" Condition="'$(IsDesktopBuild)'=='true'" />

    <Message Text="Test Executed"></Message>

    </Target>

    Basically we want to run MSTest only when running the build on a local computer.

    My questions are 1) when you run the test locally, where exactly does the test report file go Or for that matter, where does the .rtx file go whenever you run MSTest The publish commands don't seem to indicate a directory path for where the file will be.

    2) is it possible to install MSTest on our server We have the visual studio build server edition on the build server. But we don't want to install VS developer or tester edition so that the server is clean. Thanks.


  • majid12345

    How do you add the statements into the tfsbuild.proj file I wasn't able to add it.
  • dops

    1) Sorry I don't know where the report file goes by default. I think no file is generated when nothing is specified. In my case, I have been able to either give a path for my test file or ask to publish it as part of the test result

    2) You don't have MSTEST on your server

    You should have it if you want to run test. If you have the Developer Edition as I have, you can install the testing tools and so you will have MsTest



  • prashant mulay

    Note that with the migration from "Team Suite Trial" to "Team Edition for developers", you will no longer be able to open your tests results (.trx files) unless you migrate them.

    See http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=384831&SiteID=1&mode=1 for more explanations



  • acobo

    To edit TfsBuild.proj you will first need to sync it to your development machine and check it out of source control. Build Type files (including TfsBuild.proj) are stored in the BuildTypes folder just under the team project root in source control.

    -Aaron



  • Developer Edition and Builds