问题

最佳实践对如何使用reuasble测试步骤块和一个多用户的环境吗?

  • 2023年7月21日
  • 5回复
  • 10的观点
Daria
Userlevel 3
徽章 + 2
  • Daria
  • 社区负责人
  • 16日回复

你好,

什么是最好的练习如何在可重用的测试步骤块一起工作吗?

我们现在有一个图书馆但是为了改变一个块的内部图书馆用户查看完整的图书馆。
其他用户现在锁定的工作与其他块。

人们创建多个库吗?或者有什么诀窍只有块你想编辑检查吗?

质量超出测试
Hi All,<\/p>

what is the best practice on how to work together in reusable test step blocks?<\/p>

We now have a library but in order to change a block that's inside the library the user has to check out the complete library.
Other users are now locked out of working with the other blocks.<\/p>

Do people create multiple libraries? Or is there a trick to only get the block you want to edit checked out?
\u00a0<\/p>","quoteUsername":"Daria","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

5回复

C
Userlevel 3
徽章 + 2

一些用户也有类似的问题:

我问自己同样的问题…
我至少有一个更大的文件夹结构和许多(小)图书馆在这些文件夹但是它可能发生,两人可以想工作可重用的测试步骤2日在一个图书馆…
非常奇怪的事情,必须检查整个图书馆而不是一个可重用的一步。

Some users have similar questions:<\/p>

\u00a0<\/p>

I asked myself the same question...
I have at least a bigger folder structure with many (smaller) libraries within these folders but nevertheless it could happen that two people could want to work on 2 reusable test steps within one library...
Very strange thing that you have to check out the whole library instead of just one reusable step.\u00a0\u00a0<\/p>","quoteUsername":"Community Administrator","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

C
Userlevel 3
徽章 + 2

另一个观点是:

我想知道为什么不同的人应该同时RTSB特别是当他们是结构化的几个库。RTSBs必须非常小心地处理任何变化适用于所有这些RTSBs的用法。所以改变这些中心组件(至少在结构良好的图书馆概念)是由一个人完成的。否则你可能会考虑到重组库。所以要清楚:没有办法查看RTSB。

Another point of view is:<\/p>

I'm wondering why different people should work on RTSB at the same time especially when they are structured over several libraries. RTSBs have to be handled very carefully as any change applies to all usages of those RTSBs. So changing these central components (at least for a well structured library concept) is done by a single person. Otherwise you might think about re-structuring your libraries. So to be clear: there's no way to just check out a RTSB.<\/p>","quoteUsername":"Community Administrator","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

Daria
Userlevel 3
徽章 + 2

另一个观点是:

我想知道为什么不同的人应该同时RTSB特别是当他们是结构化的几个库。RTSBs必须非常小心地处理任何变化适用于所有这些RTSBs的用法。所以改变这些中心组件(至少在结构良好的图书馆概念)是由一个人完成的。否则你可能会考虑到重组库。所以要清楚:没有办法查看RTSB。

你好,谢谢你的回复。但是你做了一个假设有多个库。
我们目前有一个与所有RTSB的图书馆。如果有人在一个别人不能工作。
确实可以解决通过除号RTSB的几个逻辑库,但谎言的来源我的问题如果有最佳实践工作与图书馆和RTSB多用户环境。

我个人觉得有更多的图书馆有点混乱,不是很清楚。但如果这是我们可以调整的路要走。我真的不明白为什么你不能查看辛格RTSB。我可以检查单个模块或teststep。为什么不。Annyhow。我认为我们只需要重组图书馆本身。

质量超出测试
\t

Another point of view is:<\/p>\t

I'm wondering why different people should work on RTSB at the same time especially when they are structured over several libraries. RTSBs have to be handled very carefully as any change applies to all usages of those RTSBs. So changing these central components (at least for a well structured library concept) is done by a single person. Otherwise you might think about re-structuring your libraries. So to be clear: there's no way to just check out a RTSB.<\/p>\t<\/div><\/content-quote>

Hi , thanks for your reply. But here you made an assumption that there are multiple libraries.
We are currently having one library with all our RTSB's. If somebody has to work in one other people can't.
That can indeed be solved by deviding the RTSB's over a couple of logical libraries but there lies the origin of my question if there is a best practice with working with libraries and RTSB's in a multi user environment.

Personally I find having more libraries a bit messy and not very clear. But if that is the way to go we can adjust to that. I don't really understand why you can't check out a singel RTSB. I can check out a single module or teststep. Why not that as well. Annyhow. I think we just need to reorganize the library itself.
\u00a0<\/p>","quoteUsername":"Daria","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

C
Userlevel 3
徽章 + 2

我的5分钱的最佳实践是:

有不同的库

  • 不同的技术(HTML、SAP等)
  • 每个技术堆栈中的不同应用领域(如不同的SAP模块、应用程序,应用程序B)
  • 一个常见的RTSBs每个技术堆栈
  • 等。

对于所有这些不同的库一个负责任的的人,一个副每一个,负责的Libs / RTSBs更改任何内容。所以任何变化对他们要经历这些的人。

顺便说一下:你无法付款只是TestSteps上面提到的。测试点是最小的项目检查。

希望能帮助一些。

My 5 Cent for a Best Practice is:<\/p>

Have different Libraries for<\/p>

  • different technologies (HTML, SAP, etc.)<\/li>\t
  • different app areas within each technology stack (e.g. different SAP modules, application A, application B)<\/li>\t
  • one common with RTSBs for each technology stack<\/li>\t
  • etc.<\/li><\/ul>

    And for all of these different Libraries have\u00a0one responsible<\/strong>\u00a0person and\u00a0one deputy<\/strong>\u00a0each, that is in charge of changing any content of those Libs\/RTSBs. So any change on them has to go through those person.<\/p>

    By the way: you're not able to checkout just TestSteps as you mentioned above. TestCases are the smallest item to be checked out.<\/p>

    Hope that helps a bit.<\/p>","quoteUsername":"Community Administrator","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

Daria
Userlevel 3
徽章 + 2

我的5分钱的最佳实践是:

有不同的库

  • 不同的技术(HTML、SAP等)
  • 每个技术堆栈中的不同应用领域(如不同的SAP模块、应用程序,应用程序B)
  • 一个常见的RTSBs每个技术堆栈
  • 等。

对于所有这些不同的库一个负责任的的人,一个副每一个,负责的Libs / RTSBs更改任何内容。所以任何变化对他们要经历这些的人。

顺便说一下:你无法付款只是TestSteps上面提到的。测试点是最小的项目检查。

希望能帮助一些。

哦,是的!我的缺点:D。我同时在做两件事,从来就不是一个好主意:P。
谢谢你的额外信息。我们没有这么大的环境,但这是给我一些不错的关于如何进行进一步的信息。

感谢和有一个好一个。

质量超出测试
\t

My 5 Cent for a Best Practice is:<\/p>\t

Have different Libraries for<\/p>\t

  • different technologies (HTML, SAP, etc.)<\/li>\t\t
  • different app areas within each technology stack (e.g. different SAP modules, application A, application B)<\/li>\t\t
  • one common with RTSBs for each technology stack<\/li>\t\t
  • etc.<\/li>\t<\/ul>

    And for all of these different Libraries have\u00a0one responsible<\/strong>\u00a0person and\u00a0one deputy<\/strong>\u00a0each, that is in charge of changing any content of those Libs\/RTSBs. So any change on them has to go through those person.<\/p>\t

    By the way: you're not able to checkout just TestSteps as you mentioned above. TestCases are the smallest item to be checked out.<\/p>\t

    Hope that helps a bit.<\/p>\t<\/div><\/content-quote>

    Ah yes! My bad :D. I was doing two things at the same time which is never a good idea :P.
    Thanks for the extra information. We do not have such a big environment but this is giving me some good information on how to proceed further.<\/p>

    Thanks and have a good one.<\/p>","quoteUsername":"Daria","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

回复


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"}}}">

金宝搏app官网下载
Baidu
map