罗萨里奥的手动转轮，并从失败的步骤中提出缺陷 [英] Manual runner in Rosario and raising defects from failed steps

问题描述

关于此预期工作流程的问题，这听起来像是一个令人兴奋的进步在测试集成中！

Just a question about intended workflow of this, which all sounds like an exciting step forward in test integration!

所以，我可以用我的预期结果详细说明我在测试中的测试步骤并运行我正在测试的应用程序旁边一步一步。然后，如果步骤失败，我可以将此标记为失败并在此处引发错误，这将包含所有细节，包括失败的位置和方式的步骤和屏幕截图。现在这里有关于此的问题 -

So, I can detail my test steps in the tool with my expected outcomes and run this step by step alongside the app I'm testing. Then if a step fails I can mark this as a fail and raise a bug at this point, which will carry over all the details including steps and screenshots of where and how it failed. Now here are the questions about this -

• 
  

报告将详细介绍脚本中失败的步骤数以及这些步骤的当前状态？

How much detail will the reports go into about the number of steps that have failed in a script and perhaps the current status of these?

推荐答案

Alistair，
< br>目前我们没有以可报告的方式跟踪单个步骤失败，其主要原因是数据爆炸的巨大潜力和大多数人不关心的细节水平。因此，我们有一个模型，您已经通过或未通过测试用例，或者您还没有执行它。另外，我们会跟踪一个测试用例当前正由特定人员执行的事实，但我们并没有很好地将这些测试用例暴露给用户。

就围绕特定组件分组测试用例，您可以轻松地执行此操作。如果您只是创建一个工作项来跟踪该组件，那么您可以将测试用例链接到该工作项，一旦完成，您就可以通过仓库报告该工作项的测试进度。 >
我们再次将步骤视为单独的跟踪单元，因此所有错误都是报告流程真正处理整个测试用例。

当您运行测试用例时，有一个选项将跑步者停靠在屏幕的一侧，以便更容易看到它和您正在测试的应用程序。

Alistair,

Currently we are not tracking the individual step failures in a reportable way, the primary reason for this is the huge potential for data explosion and a level of detail that most peopl wont care about.  As such we have a model that either you have passed or failed the test case or you just have not executed it yet.  In addtion we do track the fact that a test case is currently being executed by a particular person but we don't do a good job of exposing that to the user. 

As far as grouping test case around a specific component you can easily do that.  If you simply create a work item to track that component then you can link the test cases to that work item and once you have done that you will be able to report on the progress of testing on that work item in through the warehouse.

Again we don't view the step as an individual unit of tracking, therefore all bug are reporting flows really deal with the entire test case.

When you are running the test case there is an option to dock the runner to one side of the screen to make it easier to see both that and the application you are testing.

这篇关于罗萨里奥的手动转轮，并从失败的步骤中提出缺陷的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！