如何在 Visual Studio 中对针对不同平台（64 位和 32 位）的程序集进行单元测试
我有一个针对不同平台（64 位和 32 位）的 Visual Studio C# 项目。我还有一个涵盖该项目的广泛的单元测试。该项目的性质是，它生成的程序集因平台而异（不是完全限定的程序集名称，无论目标平台如何，程序集名称都是相同的）。我现在想对这些程序集进行单元测试。做到这一点的最佳方法是什么？另请注意，我必须在 hudson 上运行测试报告（代码覆盖率和单元测试）。当前的实现针对两个不同的平台有两个不同的项目，因此测试运行文件夹（带有 in /out 目录的文件夹）不会与不同图像格式的程序集混淆。请注意，我并不期待“如何在 Visual Studio 上进行单元测试、执行代码代码覆盖率”的答案。我的问题是“在 Visual Studio 中针对不同平台对程序集进行单元测试的最佳和最简单的方法是什么”。
I have a visual studio C# project targeted at different platforms (64bit and 32 bit). I also have an extensive unit test covering this project. The nature of the project is such that , the assemblies it generates differs depending on the platform(not the fully qualified assembly name, assembly names are same regardless of the targeted platform). I now want to unit test these assemblies. What is the best approach to do this? Also note that I have to run test report (code coverage and unit test) on hudson. The current implementation have two different projects for two different platforms so that test run folder (the one with in /out directories) does not mess up with assemblies of different image format. Please note that I am NOT expecting an answer for “how to unit test, perform code code coverage on Visual Studio” . My question is “What is the best and easiest way to unit test assemblies targeted at different platforms in visual studio”.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否尝试过在 x86 和 x64 操作系统上运行单元测试？尽管我应该指出，除了少数事情外，代码的行为将完全相同，但两个重要的例外是使用注册表和处理特定于平台的不安全代码（即句柄）。
老实说..你似乎已经知道你需要做什么。
Have you simply tried running your unit tests on a x86 and a x64 operating system? Although I should point out except for a small minority of things, the behavior of your code will behave exactly the same, two important exceptions are working with the registry and dealing with say unsafe code ( i.e. Handles ) which are platform specfic.
Honestly..You seem to already know what you need to do.
如果可能的话，我实际上会将程序集制作为 Any-CPU（当然，您可能会进行一些 32/64 互操作，这意味着您已经设置了 CPU 目标，但否则让它们与 CPU 无关），并让执行进程决定架构即 32/64 位。这将迅速减少您必须测试的组件数量。
MSTest (VS2010) 应该能够处理 32 和 64，因为它会根据需要将此工作分配给 QTAgent(32).exe。 NUnit 有 2 种控制台类型，一组在任何 cpu 上运行，用于在 32 和 64 上运行，另一种固定在 32 位上，用于在 64 位平台上测试 32 位程序集。其他测试工具可能有自己的方法或使用我描述的两种方法之一。
您可以在 hudson 中使用的覆盖工具：
还有其他可能合适的工具，但我还没有使用过它们，所以我无法评论它们是否适合通过 hudson 使用，即 Visual Studio 中的那个可以是命令行驱动的。
I would actually make the assemblies Any-CPU, if possible (of-course you may some 32/64 interop that means you have set the CPU target, but otherwise let them be CPU agnostic), and have the executing process decide on the architecture i.e 32/64 bit. That will rapidly cut down on the number of assemblies you have to test.
MSTest (VS2010) should be able to handle both 32 and 64 as it farms this work out to QTAgent(32).exe as appropriate. NUnit has 2 console types one set at any-cpu for running on 32 and 64 and one fixed at 32 bit for testing 32 bit assemblies on 64 bit platforms. Other testing tools may have their own approach or use one of the two I have described.
Coverage tools you could use in hudson:
There are others that may be appropriate but I haven't used them so I can't comment on their suitability for use via hudson i.e. perhaps the one in visual studio can be command-line driven.