解决了

模板不能用于业务参数

  • 2023年7月31日
  • 1回复
  • 4的观点

Userlevel 5
徽章 + 2
  • 社区经理
  • 72回复

这就跟你问声好!

刚意识到,模板不能结合业务参数。

解决这个问题吗?

图像

步骤重新创建

1。创建一个TestCase1 Library1

2。创建一个与TestSheet1 Template1和链接

3所示。创建一个TemplateInstance1并运行它。

- - - - - - - - - - - -没问题! ! !- - - - - - - - - - - - - - - - - -

4所示。现在添加BusinessParameter Library1

5。池TemplateInstance1并运行它

- - - - - -失败! ! !- - - - - -

根本原因

1。{XL[交易]}不再是翻译

2。EnterCompanyCode正在成为一个参考,

而不是在TemplateInstance1身体功能

(最初要求和解决支持中心)

图标

最佳答案社区管理员2023年7月31日16:01

A few thoughts on your issue.<\/p>

1. ReusableTeststepBlock (RTSB)- {XL[]} vs. {PL[]}<\/strong><\/p>

Business Parameters are only available in RTSBs. Once you have decided to use them, {XL[]} references don't work anymore when you call them\u00a0directly<\/u>\u00a0on a test step in your RTSB. That's how Tosca works. Instead you can hand over the {XL[]} to the business parameter or buffer them in advance and hand over the buffer to the business parameter.<\/p>

\u00a0<\/p>

Example 1 -\u00a0Doesn't Work\u00a0- {XL[]} will not be resolved anymore, since you are using both, {XL[]} and {PL]} in parallel directly on teststeps<\/strong><\/p>

\"1fa9ea3047de19107e155752e36d43ac.iix\"<\/p>

\u00a0<\/p>

Example 2 -\u00a0Works\u00a0- Once you start instantiation {XL[] reference will be resolved since it's been called in a business parameter<\/strong><\/p>

\"cb2a66f047de19107e155752e36d434d.iix\"<\/p>

\u00a0<\/p>

Example 3 -\u00a0Works\u00a0- If you only use {XL[]} references in a RTSB and no business parameters, {XL[]}'s get resolved, once you start instantiation<\/strong><\/p>

\"b9baeab447de19107e155752e36d4352.iix\"<\/p>

\u00a0<\/p>

Example 4 -\u00a0Works\u00a0- Inside \/ Outside of an RTSB in parallel<\/strong><\/p>

\"87623af4479259107e155752e36d430b.iix\"<\/p>

\u00a0<\/p>

2. What to put in an {XL[]} reference<\/strong><\/p>

Only put testdata in your testcase design sheet and not screens, functions and SAP transaction codes you want to call (like PA30, SA38..). Make them static in the test step itself, because most of the time they are not underlying any changes within your different testcase of your testsheet. Note, you can call RTSBs within RTSBs. We have made the SAP -\u00a0 Transaction Call an RTSB and put all possible transactions to call in a value range of the business parameter. That way you can easily select them via drop down menu when you use it in your template.<\/p>

\u00a0<\/p>

\u00a0<\/p>

\"e7ee623c471259107e155752e36d43a6.iix\"<\/p>

\u00a0<\/p>

\"a58f62fc471259107e155752e36d43bb.iix\"<\/p>

\u00a0<\/p>

3. Not very helpful option - Turn it off :)<\/strong><\/p>

That option if set on \"True\" auto-assigns \/ maps {XL[]} attributes with you module attributes within your template, once you connect it with a test case design sheet. That's super inaccurate and not reliable, since Tosca isn't only connecting 100% matches but also attributes which not even match 50% or lower.<\/p>

\"f4703a78475259107e155752e36d4343.iix\"<\/strong><\/p>

That's it for the moment.<\/p>","className":"post__content__best_answer"}">

查看原始

1回复

Userlevel 3
徽章 + 2

一些想法在你的问题。

1。ReusableTeststepBlock (RTSB) - {XL[]}和{PL []}

仅可在RTSBs业务参数。一旦你决定使用它们,{XL[]}引用不再工作了,当你调用它们直接在你的测试步骤RTSB。这是托斯卡是如何工作的。相反你可以交出{XL[]}业务参数或缓冲提前和缓冲交给业务参数。

示例1 -不工作- {XL[]}将不会得到解决了,既然你都使用,{XL[]}和{PL]}直接在teststeps平行

1 fa9ea3047de19107e155752e36d43ac.iix

例2 -作品-一旦你开始实例化{XL[]引用将得到解决,因为它被称为在业务参数

cb2a66f047de19107e155752e36d434d.iix

示例3——作品——如果你只使用{XL[]}引用RTSB和业务参数,{XL []}’s得到解决,一旦你开始实例化

b9baeab447de19107e155752e36d4352.iix

例4 -作品内部/外部的RTSB平行

87623 af4479259107e155752e36d430b.iix

2。什么在一个{XL[]}引用

只把testdata testcase设计表而不是屏幕,功能和SAP交易代码你想调用(如PA30 SA38 . .)。静态测试步骤本身,因为大多数时间他们没有潜在的任何改变在你不同testsheet testcase。注意,你可以叫RTSBs RTSBs之内。我们取得了SAP -事务调用一个RTSB,把所有可能的事务调用的值范围的业务参数。这样你可以很容易地通过下拉菜单选择他们,当你使用它在你的模板。

e7ee623c471259107e155752e36d43a6.iix

a58f62fc471259107e155752e36d43bb.iix

3所示。不是非常有用的选项,把它关掉:)

这个选项如果设置在“真正的”auto-assigns /地图和你{XL[]}属性模块属性模板内,一旦连接与一个测试用例设计表。超级的不准确和不可靠的,因为托斯卡不仅连接100%匹配但也属性不匹配的50%或更低。

f4703a78475259107e155752e36d4343.iix

就是这样的时刻。

回复


Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu