本文介绍了使用TFS 2010进行Windows Embedded Compact 7 C ++应用程序测试驱动开发,单元测试和代码覆盖的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好。  我正在寻找有关最佳实践的信息,以及使用TFS 2010作为源代码管理和构建系统的Windows Embedded Compact 7上的本机应用程序的测试驱动开发,可以轻松设置和维护哪些工具。

Hello.  I am looking for information on best practices and what tools can be easily setup and maintained for test driven development of native applications on Windows Embedded Compact 7 using TFS 2010 as our Source Control and build system.

 

背景信息:

*该项目涉及自定义硬件和BSP,我们将使用CTK测试自定义驱动程序和平台。

* The project involves custom hardware and BSP, which we will be using the CTK for testing the custom drivers and the platform.

*应用程序开发将非常模块化,每个模块的开发都需要首先创建单元测试,并且只有在完成模块的完整开发之后集成到应用程序的其余部分,因此很容易开发
单元测试并在开发应用程序模块时快速执行它们。

* The application development will be very modular, and development of each module will require the unit tests be created first and only after the complete development of the module will it be integrated into the rest of the application, so easily developing the unit tests and quickly executing them as the application module is developed is required.

*开发的应用程序将是C ++和最有可能的是OS Design的子项目,以便出于性能原因将它们构建为ARMv7。  (据我所知,如果您导出SDK并使用VS2008编译器进行构建,那么您对ARMv4i的限制为
。)

* The applications developed will be C++ and most likely be sub projects of the OS Design to take advantage of building them as ARMv7 for performance reasons.  (As I understand it, if you export a SDK and build using the VS2008 compiler, you are limited to ARMv4i.)

*我们的目标是尽可能多地集成尽可能进入TFS 2010构建系统和报告。  我们目前使用Telerick TFS项目仪表板()
并希望此处显示代码覆盖率数据。

* Our goal is to integrate as much as possible into TFS 2010 build system and reports.  We currently use the Telerick TFS Project Dashboard (http://www.telerik.com/community/labs/tfs-work-item-manager-and-tfs-project-dashboard.aspx) and would like to have Code Coverage data shown here.

*我们希望尽可能使用Microsoft Tools或可靠的开源工具,因为与VS2008和TFS 2010的集成,支持和预算对我们很重要(我们都拥有MSDN Ultimate许可证)已经)。

* We would like to use Microsoft Tools or reliable open source tools if possible, as integration into VS2008 and TFS 2010, support, and budget are important to us (we all have MSDN Ultimate licenses already).

 

对我们来说最好的情况是在本地构建和单元测试应用程序开发作为桌面win32代码以获得速度和易于开发,然后在目标平台(Virtual PC VM和目标ARM硬件)上本地运行单元测试,并且还使用代码覆盖率数据自动运行
所有单元测试与夜间TFS构建(可能在Virtual PC VM上)生成并显示(最好在Telerick TFS Dashbo中ARD)。  当然,我们会根据不同平台的需要开发模拟。  问题:
 这甚至可能吗?  如果是这样,设置和维护有多难?  若否,我们需求的最大限制因素是什么?

The best case for us would be to build and unit test the application development locally as desktop win32 code for speed and ease of development, then run unit tests locally on target platforms (both Virtual PC VMs and target ARM hardware), and ALSO run all unit tests automatically with the nightly TFS build (probably on Virtual PC VMs) with code coverage data generated and displayed (preferably in Telerick TFS Dashboard).  Of course we would develop mocks as needed for different platforms.  QUESTIONS:  Is that even possible?  If so, how difficult to setup and maintain?  If not, what is the most limiting aspect of our needs?

 

我尝试使用VS2008 Team Suite版本来设置测试项目,以测试作为OS设计的子项目的C ++静态库,但是我无法让测试项目链接到静态库。  我按照这个
博客的建议,这是针对VS2010 C ++ win32:  http://blogs.msdn.com/b/jsocha/archive/2010/11/19/writing-unit-tests-in - 视觉工作室换本机c.aspx
 这让我相信微软没有单独测试本机应用程序的解决方案,这些应用程序是Windows Embedded Compact 7操作系统设计的子项目。问题: 这是正确的吗?  若然,我可以使用哪些其他工具?

I have tried to setup a test project using VS2008 Team Suite edition to test a C++ static library that is a sub project to an OS design, however I could not not get the test project to link to the static library.  I followed the advice on this blog, which is for VS2010 C++ win32:  http://blogs.msdn.com/b/jsocha/archive/2010/11/19/writing-unit-tests-in-visual-studio-for-native-c.aspx.  This leads me to believe that Microsoft does not have a solution for unit testing native applications that are a sub project of an OS design of Windows Embedded Compact 7.  QUESTIONS:  Is that correct?  If so, what other tools can I use?

 

感谢您提供的任何帮助,非常感谢!

Thanks for any help you can provide, it is most appreciated!

推荐答案

Rob

 


这篇关于使用TFS 2010进行Windows Embedded Compact 7 C ++应用程序测试驱动开发,单元测试和代码覆盖的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-29 08:05