If you are trying to introduce SCRUM have a read of Scrum from the trenches it helped me enormously. The definition of the user stories etc being done should involve passing tests and I am sure your tester will be key to deciding on when a feature is done.
I have never worked on a team where testing was more in focus than when using scrum. As the other answers state, testing should be a part of the done criteria of the sprint item.
I've had good experience with the rule, that definition of system and user tests should be written as the first activity of a sprint item. Also, no item should be accepted as done without the proper level of unit and integration tests.
This implicitly means that an item should not be "doned" by the persons that the solved the item. IMHO, that should be the responsibility of other members of the sprint team -- in your case it could be the tester.
Is testing good thing? Yes! Then do it all the time!
"Testing phase" is a term from waterfall projects.
In agile (I assume you trying to be agile since you are setting up as a scrum team) you are focused on being able to adapt and adopt quickly - testing is the key in that process.
Do it often and do it all the time - feedback will be provided often and team will be able to adopt quickly and timely.
Creating a testing phase (whenever it is scheduled for) - you will slip into waterfall mode or better yet - scrumfall. Think about the feedback - at the end of the 'testing [phase' which some after many other phases. Lots of waste that you trying to avoid by being agile and by using scrum.
There are no people with primary skills being testing - it does not matter - let them learn how to test their product/application. Invest time (and money) in that - it will pay off big time as they move forward.
There is no test phase.. test is part of each iteration..
but above is in theory.. in practice you may have important dates by which you will like to ship something - so sometimes teams label iteration(s) close to such dates as stabilization iterations where no new features are added and only must fix bugs are done..
发布评论
评论（5）
如果您想引入 SCRUM，请阅读来自战壕的 Scrum< /a> 这对我帮助很大。正在完成的用户故事等的定义应该涉及通过测试，我相信您的测试人员将是决定何时完成功能的关键。
If you are trying to introduce SCRUM have a read of Scrum from the trenches it helped me enormously. The definition of the user stories etc being done should involve passing tests and I am sure your tester will be key to deciding on when a feature is done.
在我工作过的团队中，测试比使用 Scrum 更受关注。正如其他答案所述，测试应该是冲刺项目完成标准的一部分。
我对规则有很好的经验，系统和用户测试的定义应该写成冲刺项目的第一个活动。此外，如果没有适当级别的单元和集成测试，任何项目都不应被接受。
这隐含地意味着某个项目不应该由解决该项目的人“完成”。恕我直言，这应该是冲刺团队其他成员的责任——在你的情况下，它可能是测试人员。
问候，
莫滕
I have never worked on a team where testing was more in focus than when using scrum. As the other answers state, testing should be a part of the done criteria of the sprint item.
I've had good experience with the rule, that definition of system and user tests should be written as the first activity of a sprint item. Also, no item should be accepted as done without the proper level of unit and integration tests.
This implicitly means that an item should not be "doned" by the persons that the solved the item. IMHO, that should be the responsibility of other members of the sprint team -- in your case it could be the tester.
Regards,
Morten
每个待办事项列表项都应该在被视为“完成”之前进行测试，即测试是在冲刺期间完成的。
如果您将“测试”称为“演示”，则应该在冲刺结束时完成，并有产品所有者、客户（和其他负责人）在场。
Every backlog item should be tested before considered "done", i.e. the testing is done during the sprint.
If you refer to "test" as the "demo", it should be done at the end of the sprint, with product owner, customer (and other people in charge) present.
测试是好事吗？是的！然后一直这样做！
“测试阶段”是瀑布项目中的术语。
在敏捷中（我假设你试图变得敏捷，因为你正在组建一个 Scrum 团队），你专注于能够快速适应和采用 - 测试是该过程中的关键。
经常做并且一直做——经常提供反馈，团队将能够快速及时地采用。
创建一个测试阶段（无论何时安排） - 您将进入瀑布模式或更好 - scrumfall。想想反馈——在“测试[阶段”结束时，有些阶段是在许多其他阶段之后。您试图通过敏捷和使用 Scrum 来避免大量浪费。
没有人具有主要技能进行测试 - 没关系 - 让他们学习如何测试他们的产品/应用程序。投入时间（和金钱）——随着他们的前进，这将带来巨大的回报。
Is testing good thing? Yes! Then do it all the time!
"Testing phase" is a term from waterfall projects.
In agile (I assume you trying to be agile since you are setting up as a scrum team) you are focused on being able to adapt and adopt quickly - testing is the key in that process.
Do it often and do it all the time - feedback will be provided often and team will be able to adopt quickly and timely.
Creating a testing phase (whenever it is scheduled for) - you will slip into waterfall mode or better yet - scrumfall. Think about the feedback - at the end of the 'testing [phase' which some after many other phases. Lots of waste that you trying to avoid by being agile and by using scrum.
There are no people with primary skills being testing - it does not matter - let them learn how to test their product/application. Invest time (and money) in that - it will pay off big time as they move forward.
没有测试阶段.. 测试是每次迭代的一部分..
但以上是理论上的.. 在实践中，您可能有重要的日期，您希望在该日期之前交付某些东西 - 因此有时团队会将迭代标记为接近这些日期作为稳定迭代，不添加任何新功能，只需要修复错误。
There is no test phase.. test is part of each iteration..
but above is in theory.. in practice you may have important dates by which you will like to ship something - so sometimes teams label iteration(s) close to such dates as stabilization iterations where no new features are added and only must fix bugs are done..