如何做好代码TFS审查? [英] How to do Code Reviewing with TFS?

查看:176
本文介绍了如何做好代码TFS审查?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

可能重复:结果
基于Web的代码审查工具,Team Foundation Server的

我们有大约4开发人员和我们使用TFS源控制。

We have about 4 developers and we're using TFS for source control.

我们想介绍代码审查,这样的检查在代码由同行成员性能,设计和标准进行审查。

We'd like to introduce Code Reviewing so that the checked in codes are reviewed by peer members for performance, design and standards.

什么工具,你会推荐我们使用帮助呢? (开源和免费的希望)

What tool would you recommend we use to help this? (open source and free hopefully)

我发现这个来自谷歌:的http:// teamreview .codeplex.com / ,我想测试它是如何工作的。

I found this from Google: http://teamreview.codeplex.com/ and I'm trying to test how it works.

谢谢,

推荐答案

我不知道这将如何适用于你,但在这里不用。我改变了我们的WIT过程模板(使用TFS 电动工具),这样的代码办理入住手续后的状态是等待代码审查。那么你需要指定这个WI给谁移动它到,如果代码审查是确定的,还是回如果它失败分配了关闭状态的其他用户。

I'm not sure how this will apply to you, but here goes. I changed our WIT process template (using the TFS power tools) so that the state after code check-in is "Awaiting Code Review". You then need to assign this WI to another user who moves it onto the "Closed" state if the code review is OK, or back to assigned if it's failed.

所以,这个过程转变现在是这样的:

So the process transitions are now something like:


Assigned --Check-In--> Code Review --Success--> Closed
    ^-------Failed---------|

这是远远不够完善,这在很大程度上是基于我们与Subversion和一个单独的bug跟踪系统中的进程,但它的工作原理。

This is far from perfect, and it's largely based on the processes we had with Subversion and a separate bug tracking system, but it works.

在其他消息方面,VS 11看起来有这样的开箱(也这里 - 从埃瓦尔德的回答)

In other news, VS 11 looks to have this out of the box (also here - taken from Ewald's answer).

这篇关于如何做好代码TFS审查?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆