如何告诉 MSTEST 运行解决方案中的所有测试项目？

发布于 2024-07-27 18:05:23 字数 905 浏览 7 评论 0原文

我需要知道如何告诉 MSTEST 运行解决方案文件中的所有测试项目。这需要从命令行完成。现在我必须向它传递一个特定的项目文件，我试图让它从解决方案文件运行。

我希望这是可能的，因为在 Visual Studio 中，按 Ctrl+R、A 可以运行当前打开的解决方案中的所有测试。

按照我解释帮助文件的方式，您必须专门传入每个 DLL。

我想从 CruiseControl.NET 服务器的命令行运行它，这样我就可以编写其他实用程序来实现这一点。如果有一种奇怪的方法可以通过其他方法实现这一点，请告诉我。

如何告诉 MSTEST 运行解决方案的所有测试项目？

<exec>
    <!--MSTEST seems to want me to specify the projects to test -->
    <!--I should be able to tell it a SOLUTION to test!-->
    <executable>mstest.exe</executable>
    <baseDirectory>C:\projects\mysolution\</baseDirectory>
    <buildArgs>/testcontainer:testproject1\bin\release\TestProject1.dll 
    /runconfig:localtestrun.Testrunconfig 
    /resultsfile:C:\Results\testproject1.results.trx</buildArgs>
    <buildTimeoutSeconds>600</buildTimeoutSeconds>
</exec>

原文

I need to know how to tell MSTEST to run all test projects in a solution file. This needs to be done from the command line. Right now I have to pass it a specific project file, I'm trying to get it to run from a SOLUTION file.

I'm hoping this is possible, because in Visual Studio, hitting Ctrl+R, A, runs ALL tests in the currently opened solution.

The way I've interpretted the help files, you have to pass in each DLL specifically.

I want to run this from the command line from my CruiseControl.NET server, so I can write other utilities to make this happen. If there is a wierd way of getting this to happen through some OTHER method, let me know.

How do I tell MSTEST to run all test projects for a solution?

<exec>
    <!--MSTEST seems to want me to specify the projects to test -->
    <!--I should be able to tell it a SOLUTION to test!-->
    <executable>mstest.exe</executable>
    <baseDirectory>C:\projects\mysolution\</baseDirectory>
    <buildArgs>/testcontainer:testproject1\bin\release\TestProject1.dll 
    /runconfig:localtestrun.Testrunconfig 
    /resultsfile:C:\Results\testproject1.results.trx</buildArgs>
    <buildTimeoutSeconds>600</buildTimeoutSeconds>
</exec>

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

草莓酥 2024-08-03 18:05:23

为了详细说明 VladV 的答案并使事情更加具体，按照建议的命名约定，可以使用 MSBuild. 我当前项目的 msbuild 文件中的以下代码片段完全符合您的要求。

<Target Name="GetTestAssemblies">
    <CreateItem
        Include="$(WorkingDir)\unittest\**\bin\$(Configuration)\**\*Test*.dll"
        AdditionalMetadata="TestContainerPrefix=/testcontainer:">
       <Output
           TaskParameter="Include"
           ItemName="TestAssemblies"/>
    </CreateItem>
</Target>
<!-- Unit Test -->
<Target Name="Test" DependsOnTargets="GetTestAssemblies">
    <Message Text="Normal Test"/>
<Exec 
    WorkingDirectory="$(WorkingDir)\unittest"
    Command="MsTest.exe @(TestAssemblies->'%(TestContainerPrefix)%(FullPath)',' ') /noisolation /resultsfile:$(MSTestResultsFile)"/>
    <Message Text="Normal Test Done"/>
</Target>

此外，将 MsBuild 与 CruiseControl 集成也是小菜一碟。

编辑
以下是如何从 ccnet.config 中“调用”msbuild。

首先，如果您尚未使用 MSBuild 进行构建自动化，请添加将

<Project DefaultTargets="Build"
    xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    ..... <insert snippet here> .....
</Project>

其保存在源代码树中解决方案旁边的例如 RunTests.proj 中。现在您可以将上面的 ccnet.config 部分修改为以下内容：

<msbuild>
  <executable>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe</executable>
  <workingDirectory>C:\projects\mysolution\</workingDirectory>
  <baseDirectory>C:\projects\mysolution\</baseDirectory>  
  <projectFile>RunTests.proj</projectFile>
  <targets>Test</targets>
  <timeout>600</timeout>
  <logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger>
</msbuild>

To elaborate on VladV's answer and make things a bit more concrete, following the suggested naming convention running your tests can be easily be automated with MSBuild. The following snippet from the msbuild file of my current project does exactly what you asked.

<Target Name="GetTestAssemblies">
    <CreateItem
        Include="$(WorkingDir)\unittest\**\bin\$(Configuration)\**\*Test*.dll"
        AdditionalMetadata="TestContainerPrefix=/testcontainer:">
       <Output
           TaskParameter="Include"
           ItemName="TestAssemblies"/>
    </CreateItem>
</Target>
<!-- Unit Test -->
<Target Name="Test" DependsOnTargets="GetTestAssemblies">
    <Message Text="Normal Test"/>
<Exec 
    WorkingDirectory="$(WorkingDir)\unittest"
    Command="MsTest.exe @(TestAssemblies->'%(TestContainerPrefix)%(FullPath)',' ') /noisolation /resultsfile:$(MSTestResultsFile)"/>
    <Message Text="Normal Test Done"/>
</Target>

Furthermore integrating MsBuild with CruiseControl is a piece of cake.

Edit
Here's how you can 'call' msbuild from your ccnet.config.

First if you do not already use MSBuild for your build automation add the following xml around the snippet presented earlier:

<Project DefaultTargets="Build"
    xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    ..... <insert snippet here> .....
</Project>

Save this in e.g. RunTests.proj next to your solution in your source tree. Now you can modify the bit of ccnet.config above to the following:

<msbuild>
  <executable>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe</executable>
  <workingDirectory>C:\projects\mysolution\</workingDirectory>
  <baseDirectory>C:\projects\mysolution\</baseDirectory>  
  <projectFile>RunTests.proj</projectFile>
  <targets>Test</targets>
  <timeout>600</timeout>
  <logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger>
</msbuild>

回复收藏 0 原文

抱猫软卧 2024-08-03 18:05:23

这是一个旧线程，但我一直在努力解决同样的问题，我意识到你真的可以在整个解决方案中的每个 dll 上运行 MSTest，并且它不会真正引起任何问题。 MSTest 正在用 [TestMethod] 属性标记的程序集中查找方法，而不是“测试”程序集的程序集不会有任何用该属性修饰的方法。所以你会得到一个“没有要执行的测试”。回复消息并没有造成任何伤害。

例如，在 NAnt 中，您可以这样做：

<target name="default">
    <foreach item="File" property="filename">
        <in>
            <items>
                <include name="**\bin\Release\*.dll" />
            </items>
        </in>
        <do>
            <echo message="${filename}" />
            <exec program="C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe">
                <arg value="/testcontainer: ${filename}" />
                <arg value="/nologo" />
            </exec>
        </do>
    </foreach>
</target>

它将运行解决方案中每个 bin\Release 文件夹中每个 dll 中的所有测试方法。那些不是测试 dll 的文件将返回“没有要执行的测试”。那些有测试的将运行测试。我唯一还没有弄清楚的部分是（在 NAnt 中）命令第一次返回非零值时执行会停止。因此，如果任何单元测试失败，它不会继续在后续程序集中执行任何测试。这不太好，但如果所有测试都通过，那么它们都会运行。

This is an old thread, but I have been struggling with the same issue and I realized that you can really just run MSTest on every dll in the whole solution and it doesn't really cause any problems. MSTest is looking for methods in the assemblies marked with the [TestMethod] attribute, and assemblies that aren't "test" assemblies just won't have any methods decorated with that attribute. So you get a "No tests to execute." message back and no harm done.

So for example in NAnt you can do this:

<target name="default">
    <foreach item="File" property="filename">
        <in>
            <items>
                <include name="**\bin\Release\*.dll" />
            </items>
        </in>
        <do>
            <echo message="${filename}" />
            <exec program="C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe">
                <arg value="/testcontainer: ${filename}" />
                <arg value="/nologo" />
            </exec>
        </do>
    </foreach>
</target>

and it will run all the test methods in every dll in every bin\Release folder in the solution. Those which are not test dlls will return a "No tests to execute." and those that have tests will have the tests run. The only part I haven't figured out yet is that (in NAnt) execution stops the first time a command returns a non-zero value. So if any unit tests fail it doesn't keep going to execute any tests in subsequent assemblies. That is not great, but if all the tests pass, then they will all run.

回复收藏 0 原文

情归归情 2024-08-03 18:05:23

我最近刚刚解决这个问题。这是我的建议：使用 mstest 的 testmetadata + testlist 选项

首先，您应该在 testmetadata 文件（vsmdi）中创建一个测试列表，
命令行应该是 mstest /testmetadata:....vsmdi /testlist:
然后使用ccnet config运行mstest

回复收藏 0 原文

小苏打饼 2024-08-03 18:05:23

我知道这个帖子已经很老了，但它在谷歌上的排名仍然很高，所以我想我可以帮助一两个。
无论如何，因为对此没有令人满意的解决方案。
我为此编写了一个 msbuild 任务。
详细信息可以在这里找到：
http://imistaken.blogspot.com/2010/ 08/running-all-tests-in-solution.html

回复收藏 0 原文