使编码的UI测试在真正的TFS生产构建中工作

大家好，

我正在开发一个包含客户端（WPF），服务器（WCF服务）和Web服务的大规模系统解决方案。为了测试WPF客户端，我编写了一个编码的UI测试。现在，我希望能够在构建代理程序的构建过程中启动我的客户端应用程序
的新构建版本。我们有几个代理（32位和64位）构建多个版本的客户端（调试/发布）。我已经阅读了Microsoft提供的文档，但这实际上归结为对calculator.exe
进行简单测试以及如何使构建/测试代理以交互方式运行。

I am working on a large scale system solution that incorporates a client (WPF), server (WCF service) and a webservice. To test the WPF client I have written a coded UI test. Now I want to be able to launch the newly build version of my client application as part of the build on the build agents. We have several agents (32bit and 64bit) building several versions of the client (debug/release). I have read the documentation provided by Microsoft, but that really boils down to making simple tests on the calculator.exe and how to make the build/test agents run interactively.

我还在这个论坛和stackoverflow（http://stackoverflow.com/questions/2776774/vs-2010-coded-ui-test-launch-referenced-application）上看到了一个回复，建议将所有输出文件添加为链接测试项目。这不是生产环境中真正严重的
选项，因为客户端具有各种配置和资源文件。此外，我没有看到它如何与调试/发布版本一起工作，因为链接将指向特定的构建输出。

I also saw a reply on this floating around this forum and stackoverflow (http://stackoverflow.com/questions/2776774/vs-2010-coded-ui-test-launch-referenced-application) suggesting adding all output files as links to the test project. This not really a serious option in a production environment since the client has all sorts of configuration and resource files. Furthermore I fail to see how this would work with debug/release versions, since the link would point to a specific build output.

我真的想要一个关于如何分步指导编写一个Coded UI测试，启动在本地和TFS构建代理（或测试代理，如果有必要）的TestInitialize方法中构建的应用程序。

I would really like a step-by-step guide on how to write a Coded UI test that launches the application being built in the TestInitialize method that works locally and on TFS build agents (or test agents, if that is necessary).

我希望"启用部署"在testsettings中（由于使用TFS自动构建的编码UI测试，所记录的功能最少）将以某种方式使我能够访问正在构建的.exe文件？除了VS2010中的稀疏UI之外，编辑构建
定义（或生成的ms构建文件）的那种或某种方式。我很惊讶这种情况没有更好的记录？能够从编码的UI测试中从构建输出中启动某些东西似乎非常相关吗？

I'm hoping the "Enable Deployment" in the testsettings (the least documented feature ever, since using Coded UI tests with TFS automated builds) will somehow enable me to access the .exe file being built? Either that or some way to edit the build definition (or the resulting ms build file) aside from the sparse UI in VS2010. I'm very surprised that this scenario has not been documented better? It seems very relevant to be able to launch something from the build output from a coded UI test?

提前感谢您对此的任何答案..

Thanks in advance for any kind of answer on this..

/ Lasse