TFS2010 测试用例中的富文本测试步骤'文本?

发布于 11-19 13:54 字数 378 浏览 6 评论 0原文

我目前正在评估 Microsoft 的 Test Manager 2010 TestStep Editor 控件中的限制的可能解决方案,我想知道是否有人知道是否以及如果是这样,如何将富文本写入步骤的“操作”和“预期结果”字段?据我所知,它需要 'ParameterizedString< /a>' 作为输入,但我不确定 MSDN 在说“[...]代表具有嵌入参数的字符串。[...]”时指的是哪些参数(或 MTM TestRunner 可以处理)。

I am currently evaluating possible solutions to limitations in Microsoft's Test Manager 2010 TestStep Editor control and I was wondering whether anyone knows if and if so, how you can write richtext to the Action and Expected Result fields of a step? As far as I saw it takes a 'ParameterizedString' as input, but I am not sure what parameters MSDN refers to (or the MTM TestRunner can handle) when saying "[...]Represents a string that has embedded parameters.[...]".

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

陈独秀2024-11-26 13:54:00

预期结果字符串是由空格、分号或逗号分隔的字符串名称列表。您可以输入类似以下内容:@Test、@Cart、@Book 或 @Test @Cart @Book。

您无法将 HTML 添加到预期结果参数或操作;但是,我不确定是否会将其描述为限制。您认为需要采取什么行动才能做到这一点。操作通常是“单击此”或“转到此处”您是否只想为操作的某些部分提供更强的视觉队列?

这是一篇文章,描述了预期结果部分:

测试用例的真正威力来自于
屏幕上的“步骤”选项卡上。这是您列出手册的地方
测试人员将用来测试应用程序的步骤。从哪里开始输入
它显示“单击此处添加步骤”。在“操作”列中,您添加
测试人员应该尝试并执行的操作,例如“打开互联网
Explorer。”在预期结果列中,列出应该发生的情况
执行该操作时,例如“Internet Explorer 打开其
默认主页。”要继续向测试用例添加新步骤,请点击
输入以转到新行。

并非每个行动步骤都需要预期结果。当预期的
指定结果后,它将将该步骤转变为验证步骤。和
验证步骤,测试人员必须指定是否
特定步骤是否成功。

您可以为测试步骤提供参数。这
允许您多次运行测试,每次使用不同的
价值。一个例子是测试不同的登录值
网站。您可以不必为每次登录创建新的测试用例
创建一个测试用例,并向其中传递多个登录值。

The Expected Results string is a list of string namees delimited by spaces, semi-colons or commas. You can enter something like: @Test, @Cart, @Book or @Test @Cart @Book.

You can't add HTML to the Expected Result parameters or the action; however, I am not sure I would describe this as a limitation. What action were you thinking you would need to be able to do this. Actions are typically "Click this" or "Go to here" Did you just want a stronger visual queue for certain parts of the action?

Here is an article that describes the intent with the expected results section:

The real power of the test case though, comes in the bottom portion of
the screen, on the Steps tab. This is where you list out the manual
steps the tester will use to test the application. Start typing where
it says "Click here to add a step." In the Action column, you add the
action that the tester should try and perform, such as "Open Internet
Explorer." In the Expected Results column, you list what should happen
when the action is performed, such as "Internet Explorer opens to its
default home page." To continue adding new steps to the test case, hit
Enter to go to a new line.

Not every action step requires an expected result. When an expected
result is specified, it turns that step into a verification step. With
a verification step, the tester will have to specify whether that
particular step was successful or not.

You have the ability to provide parameters to your test steps. This
allows you to run the test multiple times, each time using a different
value. An example of this would be testing different login values on a
Web site. Instead of creating a new test case for each login, you can
create one test case, and pass multiple login values into it.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文