找到你要的答案

Q:ALM: Should code reviews and unit tests be considered as backlog item tasks?

Q:目的:将代码评审和单元测试是积压项目的任务?

I've started using TFS as my ALM with a Scrum template. Should I include code reviews and unit tests as part of the tasks of the product backlog items (user stories) or should they be considered within (as part of) the development tasks?

我开始用TFS作为我的ALM Scrum模板。我应该将代码审查和单元测试作为产品积压项目(用户故事)的任务的一部分,还是应该被视为开发任务的一部分?

answer1: 回答1:

Unit tests should be part of the development task -- you shouldn't be writing code, then writing tests for the code later. The tests should be written along with the code, and the code isn't done until it's tested.

For code review:

Again, code review isn't a separate task -- it's a requisite for a development task to be considered complete.

If you're using TFVC, install a code review check-in policy for TFVC and use the built in code review workflow.

If you're using Git, require pull requests and have the code reviewed when the pull request is submitted. In TFS 2015, you'll be able to use branch policies to enforce code reviews as well.

单元测试应该是开发任务的一部分,你不应该写代码,然后为代码编写测试。测试应该与代码一起编写,代码在测试之前没有完成。

代码审查:

再次,代码审查不是一个单独的任务-它是一个发展任务的必要性,被认为是完整的。

如果你使用的tfvc,安装tfvc代码审查登记政策和使用内置的代码审查工作流程。

如果你使用Git,需要拉要求并有代码审查时拉请求提交。在TFS 2015,你就可以使用部门政策执行代码审查和。

answer2: 回答2:

No, Code Review and Unit tests are not backlog items, not even a sprint task, those are development tasks.

I would recommend you to create the Definition of Done for your team, i.e. you can write common tasks that needs to be accomplished by the team to consider the story or defect done.

For example: - Feature is coded, submitted to the repository and code review is done. - Implementation is compliant with standards of coding. - Unit Test cover primary functionality - ....

You can share this to your team and keep improving it as the project continues. The DoD of my team has almost 30 items. That would be great to keep DoD in a common place, maybe wiki or in your workstation.

不,代码审查和单元测试不是待办事项,甚至不是一个冲刺任务,而是开发任务。

我建议你为你的团队创建完成的定义,也就是说,你可以编写团队需要完成的共同任务来考虑这个故事或缺陷。

For example: - Feature is coded, submitted to the repository and code review is done. - Implementation is compliant with standards of coding. - Unit Test cover primary functionality - ....

您可以分享这对您的团队,并继续改善它的项目继续。我的团队的国防部有近30个项目。这将使国防部在一个共同的地方,也许维基或在你的工作站。

answer3: 回答3:

In Agile methods, code Review and unit tests are indeed not Product Backlog items and should not be in the Product Backlog. However it is completely understandable and normal to incorporate those tasks into a Sprint Backlog.

To rephrase the Scrum Manual: " The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality"

在敏捷方法中,代码审查和单元测试实际上不是产品积压项目,而不应该在产品积压中。然而,将这些任务纳入Sprint的积压是完全可以理解和正常的。

To rephrase the Scrum Manual: " The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality"

answer4: 回答4:

No, it should not be part of user stores. In my opinion, they should be included as part of definition of done. When the feature is delivered - the delivered should means that not only functional part is completed but all the tests are completed as well.

不,它不应该是用户存储的一部分。在我看来,他们应该包括做的定义的一部分。当交付的功能-交付应意味着不仅功能部分完成,但所有的测试也完成。

unit-testing  tfs  scrum  vs-team-services  alm