为什么让测试用例步骤告诉您再次重复之前的步骤不好呢？
假设我有一个测试用例，其中包含一些步骤。现在，假设在完成步骤 4 和 5 后需要重复步骤 3...这样，当您执行步骤 6 时，您就处于正确的位置。
告诉测试人员重复某个步骤是一个好的做法吗？或者将重复的步骤复制并粘贴到需要重复的步骤中会更好吗？
我听到这样的争论：告诉测试人员重复步骤不是行业标准，并且如果以这种方式编写测试用例，则可能无法通过某些认证。
示例：
*第1步：点击查看事件日志按钮；预期结果：出现事件日志窗口
步骤 2：关闭事件日志窗口（X）或确定；预期结果：事件日志窗口消失
步骤3：重复步骤1；预期结果：第 1 步的预期结果
第 4 步：单击“取消”按钮；预期结果：“事件日志”窗口关闭，并且不会应用任何更改（例如清除日志）
步骤 5：重复步骤 1；预期结果：第 1 步的预期结果
第 6 步：单击“清除”按钮并单击“应用”；预期结果：日志被清除
...*
有些人认为我应该在每次需要重复步骤 1 时复制并粘贴步骤 1 中的内容，而不是简单地告诉测试人员应该重复该步骤。任何有关行业标准、潜在缺陷等的意见……将不胜感激。
Let's say I have a test case with some steps in it. Now, let's say that step 3 needs to be repeated after you complete steps 4 and 5 ... so that when you do step 6 you are in the right place.
Is it good practice to tell the tester to repeat a step? Or would it be better copy-and-paste the repeated step into the step where you would need to repeat it?
I am hearing arguments that it is not industry standard to tell the tester to repeat steps and that one might not pass certain certifications if test cases are written in this manner.
Example:
*Step 1: Click the View Event Log button; Expected Results: Event Log window appears
Step 2: Close the event log window (X) or OK; Expected Results: The Event Log window disappears
Step 3: Repeat Step 1; Expected Results: Expected Results from Step 1
Step 4: Click the Cancel button; Expected Results: The Event Log window closes and any changes (such as clearing the log) are not applied
Step 5: Repeat Step 1; Expected Results: Expected Results from Step 1
Step 6: Click the Clear button and hit apply; Expected Results: The log is cleared
...*
Some people think that I should be copying-and-pasting what is in Step 1 each time I need to repeat that step rather than just simply saying that the tester should repeat the step. Any input as to industry standards, potential downfalls, etc ... would be greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
测试用例设计并不真正遵循行业标准，如果您想获得认证，列出重复步骤是不可以的。我个人认为这是垃圾。我认为要求测试人员重复一个步骤没有问题。作为敏捷方法论的信徒，我更喜欢更简单的测试用例，这样测试人员就有更多的时间来测试场景而不是设计测试用例（或者如果您在跨职能团队中，那么开发人员有更多的时间来开发）。如果您希望从更大的测试社区获得更多意见，请尝试 http://www.qaforums.com/
Test case design does not really follow an industry standard, if you were trying to get certified, listing to repeat a step is a no-no. I personally think that's crap. I see no problem asking a tester to repeat a step. As a believer in agile methodology, I prefer much simpler test cases so a tester has more time to test scenarios rather than design test cases (or a developer more time to develop if you are in a cross functional team). If your looking for more input from a larger testing community try http://www.qaforums.com/
测试用例应尽可能独立，不要在单个测试用例中验证两个结果。测试用例的设计不应让测试人员必须重复任何先前的步骤。在这种情况下，应该编写一个新的测试用例，因为它是一条新路径。这种方法的优点是，在执行结束时，您将清楚地了解测试覆盖率和需求的通过/失败百分比，因为所有测试用例都是独立的。
Test cases should be as independent as possible and not verifying two outcomes in a single test case. The test cases should not be designed in a way where the tester has to repeat any previous step. In this case, a new test case should be written because it is a new path. The prons for this approach is that at the end of execution you'll have a clear picture of the test coverage and the pass/fail % of the requirements because all the test cases are independent.