Question

在我的工作中,我们处理越来越多的国家。我们现在重新利用ium使这些测试案例自动化,但我们正在一个有两周印本和每月释放周期的传闻小组。

每两周,我们需要管理我们的自动化设备。我们有一个专门负责这项任务的支助小组。然而,每个国家都增加了操作试验套的时间,而且我们有许多测试套。我们几乎处于关键负荷。我们只有足够时间每印花一页,我们今后几个月将超越这个范围。

是否有办法压缩每一语文的时间? 您能否从测试一种语言中得出一些一般性假设,即你可以跳上另一个语言的同一页?

具体来说,是否可加快这一进程? 我们确实必须使用许多Xpath甄选器——与发展小组合作,以获得更好的超文本布局,以便使用id/cs挑选器大大改进时间?

Answer 1

如果您有多个试验点以相同的代码进行测试,并且测试不会相互干扰,。你们应该做工作。它将作出一些额外的努力——或许是一些额外的硬件——但一旦适当配置,你能够测试的语文数量仅因硬件能够处理的同时测试次数而受到限制。

关于甄选者,移至。作为umb条的规则:在可能的情况下,使用特别安全局;XPath只能用作一种退步情景。社会保障局不提供支持的物品,例如与母子的通航,或对元素内容的对等,在有利的情况下不会犹豫使用XPath。您还应检查这些博客的相关职位:这些职位提供了一些额外的背景和移徙渠道。

Answer 2

我在一页上对目前的浏览器进行了一些检查,有500个元素,这里是我所看到的一些基准。或许应该有时间制定基准测试方案,以便定期(新的浏览器释放)检查基准。我用7台IE9和Webdriver 2.11.0检查了地雷。每次测试的系数为5倍,然后确定平均反应。

SUMMARY:FirefoxDriver [5 tries] =========================
Find By ID Avg: 169 ms
Find By Name Avg: 17 ms
Find By Relative XPath Avg: 7 ms
Find By Absolute XPath Avg: 6 ms
Find By CssSelector Avg: 6 ms
Find By ClassName Avg: 5 ms
=========================
SUMMARY:InternetExplorerDriver [5 tries] =========================
Find By ID Avg: 309 ms
Find By Name Avg: 90 ms
Find By Relative XPath Avg: 82 ms
Find By Absolute XPath Avg: 82 ms
Find By CssSelector Avg: 53 ms
Find By ClassName Avg: 75 ms
=========================

Run 争.多管,也是改善业绩的一个巨大途径。我的猜测是,有了虚拟服务器,你就能够轻易地进行多种测试,不会发生冲突。另外,如果你能够使用超文本自动驱动器,因为它比任何其他浏览器更有效率(如果你的要求表明你需要使用真正的浏览器、多个浏览器或公正的验证)。

Answer 3

你可以从其他职位和评论中看到,你可能需要在你自己的网页上做一些试验,以确定哪一种方法能最快地找到你的内容。我确实发现的一件事是,仅仅寻找后代人肯定会加快大页的步伐,因此,我们常常会找到一个集装箱元素,例如干iv,然后找到其后代:

IWebElement myDiv = myWebDriver.FindElement(By.ID("divId")); IWebElement descendant = myDiv.FindElement(By.ID("descendantId"));

关于您是否能够就不同语言和市场作出一些假设,是你们能够做到的。语言类型不同。必须测试其中每一种语文,但不一定是这些语文中的每一种语文。如果你支持的话,你将想测试含有不同特性的语文。

With that said, I think there is an important question that is not being asked, and that is... What are you getting out of running your automated tests on multiple languages? Does changing the language ever cause issues with functionality? Certain tests for date formats, etc are useful and can be automated, but if the only difference is the language, then unless you can test that the strings are translated correctly and are correct in context (which you can t unless you speak all of those languages fluently and want to maintain a massive list of strings in various languages) then it doesn t actually buy you much. I would suggest running a small subset of your automated tests in different languages and reduce the number of those different languages down to a handful based on their character sets and/or formatting differences. The biggest concerns that you have with different languages are layout issues where long strings can cause elements to grow larger than expected and cause problems. Most of these layout issues won t be caught by your automation anyways unless you have an extremely mature (and probably not cost effective) automation model that checks for page layout. You are better off getting a Pseudo-loc build that automatically enlarges strings and ensures that you are actually translating all of your text and doing one manual test pass against that pseudo loc build.

关于以多种语文核实案文的效率的相关员额和答案见:https://sqa.stack Exchange.com/questions/1949/do-you-verification-of-text-in-your-a auto-tests/1958#1958#。

友情链接