blocks|key|2117109|text|看一下等待命令，而不是睡眠-在这个网站上搜索或者Google会给你提供很多例子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Look at the Wait commands rather than sleep - a search on this site or Google will give you lots of examples

blocks|key|2117286|text|您可以使用WebDriverWait与页面加载同步。下面这样的内容可能会有所帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2117287|WebDriverWait+wait+=+new+WebDriverWait(driver,+15);+//you+can+play+with+the+time+integer++to+wait+for+longer+than+15+seconds.`
wait.until(ExpectedConditions.titleContains("title"));+//if+you+want+to+wait+for+a+particular+title+to+show+up|code-block|syntax|javascript|2117288|或|2117289|wait.until(ExpectedConditions.presenseOfElementLocated(ByLocator));+//in+case+you+want+to+wait+for+a+particular+element+to+appear+on+the+page.`|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|M|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|N|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|O|8|@]|9|@]|A|$E|F]]]|K|$]]

You can use WebDriverWait to synch with page load. Something like the following might help

<pre><code>WebDriverWait wait = new WebDriverWait(driver, 15); //you can play with the time integer to wait for longer than 15 seconds.`
wait.until(ExpectedConditions.titleContains("title")); //if you want to wait for a particular title to show up
</code></pre>

OR

<pre><code>wait.until(ExpectedConditions.presenseOfElementLocated(ByLocator)); //in case you want to wait for a particular element to appear on the page.`
</code></pre>

blocks|key|282561|text|睡眠方法几乎都是同步自动化测试的最不容易接受的方法。一种更好的方法可能是注册一个事件并检查在所需状态下引发的事件，或者使用一个轮询循环，使测试能够在系统准备就绪时继续进行(例如，出现一个元素id+)，或者，如果超过预定的最大等待时间，就会发生超时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

A Sleep method is almost always the least acceptable way to synchronize an automated test. A better approach might be to register an event and check the event is raised when in the desired state, or use a polling loop which will can enable the test to proceed when the system is ready (e.g. an element id appears), or a timeout occurs if it takes more than a pre-determined max wait time.

blocks|key|2117246|text|永远不要在考试中使用睡眠。你的每一次睡眠都预示着一个糟糕的测试设计。假设您有1000‘s的睡眠，但是加载某些东西需要1002’s-您的测试将中断。如果要花费996毫秒，那你就是在浪费时间。有人说过，我刚才在Stack+Overflow+-+WebDriver+-等待元素-+PageObject模式中回答了几乎相同的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/18843581/wait-for-elment-webdriver-pageobject-pattern/18844275#18844275^0|3C|T|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

Don't ever use sleep in your test. Every sleep you have indicates to a bad test design. Let's say you have a sleep of 1000ms, but it takes 1002ms to load something - your test will break. If it takes 996ms, you are wasting time. That been said, I just answered pretty much the same question in Stack Overflow - <a href="https://stackoverflow.com/questions/18843581/wait-for-elment-webdriver-pageobject-pattern/18844275#18844275">Wait for element - WebDriver - PageObject pattern</a>.

blocks|key|2117205|text|这段代码告诉Selenium在页面上搜索最多60秒的id-of元素。一旦它找到元素，您就可以与它交互。如果在60秒内找不到该元素，则将抛出一个java.lang.AssertionError，其原因是“超时”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2117206|for+(int+second+=+0;;+second%2B%2B){
++++++++if+(second+>=+60)
++++++++++++fail("timeout");
++++++++try{
++++++++++++if+(1+==+driver.findElements(By.xpath("//a[@id=\"id-of-element"]")).size()){
++++++++++++++++driver.findElement(By.xpath("//a[@id=\"id-of-element")).click();++++++++++++++++++++
++++++++++++++++break;
++++++++++++}
++++++++}+catch+(Exception+e){
++++++}
}|code-block|syntax|javascript|2117207|根据Kate的评论，这段代码不会产生60秒的等待时间。|2117208|要等待元素出现，我将使用隐式等待：|2117209|driver.manage().timeouts().implicitlyWait(60,+TimeUnit.SECONDS);|2117210|这意味着每当调用WaitForElement()或WaitForElements()时，驱动程序将等待60秒，以等待指定的元素出现。见http://docs.seleniumhq.org/docs/04_网络驱动程序_高级.#隐式等待和http://www.bizalgo.com/2012/01/14/timing-races-selenium-2-implicit-waits-explicit-waits/。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#implicit-waits|1|http://www.bizalgo.com/2012/01/14/timing-races-selenium-2-implicit-waits-explicit-waits/^0|0|0|0|0|0|1V|1E|0|3A|2G|1^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|14|8|@]|9|@$O|15|P|16|1|17]|$O|18|P|19|1|1A]]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

This code tells Selenium to search up to 60 seconds for id-of-element to appear on the page. Once it finds the element, you can interact with it. If the element is not found within 60 seconds, a java.lang.AssertionError will be thrown with the reason being "timeout".

<pre><code>for (int second = 0;; second++){
 if (second &gt;= 60)
 fail("timeout");
 try{
 if (1 == driver.findElements(By.xpath("//a[@id=\"id-of-element"]")).size()){
 driver.findElement(By.xpath("//a[@id=\"id-of-element")).click(); 
 break;
 }
 } catch (Exception e){
 }
}
</code></pre>

As per Kate's comment, this code will not produce a wait time of 60 seconds.

To wait for an element to appear, I would use an implicit wait:

<pre><code>driver.manage().timeouts().implicitlyWait(60, TimeUnit.SECONDS);
</code></pre>

This means that whenever you call WaitForElement() or WaitForElements(), the driver will wait up to 60 seconds for the specified element or elements to appear. See <a href="http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#implicit-waits" rel="nofollow">http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#implicit-waits</a> and <a href="http://www.bizalgo.com/2012/01/14/timing-races-selenium-2-implicit-waits-explicit-waits/" rel="nofollow">http://www.bizalgo.com/2012/01/14/timing-races-selenium-2-implicit-waits-explicit-waits/</a>.

blocks|key|282834|text|简单的ready2use片段>完美地为我工作|type|header-two|depth|inlineStyleRanges|entityRanges|data|282835|static+void+waitForPageLoad(WebDriver+wdriver)+{
++++WebDriverWait+wait+=+new+WebDriverWait(wdriver,+60);

++++Predicate<WebDriver>+pageLoaded+=+new+Predicate<WebDriver>()+{

++++++++@Override
++++++++public+boolean+apply(WebDriver+input)+{
++++++++++++return+((JavascriptExecutor)+input).executeScript("return+document.readyState").equals("complete");
++++++++}

++++};
++++wait.until(pageLoaded);
}|code-block|syntax|javascript|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|I|8|@]|9|@]|A|$E|F]]]|G|$]]

Simple ready2use snippet > Working perfectly for me 

<pre><code>static void waitForPageLoad(WebDriver wdriver) {
 WebDriverWait wait = new WebDriverWait(wdriver, 60);

 Predicate&lt;WebDriver&gt; pageLoaded = new Predicate&lt;WebDriver&gt;() {

 @Override
 public boolean apply(WebDriver input) {
 return ((JavascriptExecutor) input).executeScript("return document.readyState").equals("complete");
 }

 };
 wait.until(pageLoaded);
}
</code></pre>

blocks|key|2117309|text|在我的经验中，driver.manage().timeouts().implicitlyWait(60,+TimeUnit.SECONDS);是正确和最干净的方法。在实例化驱动程序之后调用它一次，所有后续调用都将正确等待指定的时间段(本例中为60秒)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2117310|在显式等待的时间范围内，最好是慷慨的，因为较低的环境可能有倾斜的加载时间，特别是当它是对新环境的第一对调用时。尽管如此，60秒仍然是网络应用的高端。|entityMap^0|7|1S|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|L|8|@]|D|@]|E|$]]]|H|$]]

<code>driver.manage().timeouts().implicitlyWait(60, TimeUnit.SECONDS);</code> is the correct and cleanest way of doing this in my experience. Call it once after instantiating the driver, and all subsequent calls will correctly wait for whatever timespan specified (60 seconds in this case)

It is better to be generous in timeframes for explicit waits, as lower environments can have skewed loading times, especially when it is the first couple calls to a fresh environment. That being said, 60 seconds is still on the high end for web apps.

blocks|key|2117322|text|虽然document.readyState大部分时间都能工作，而不是依赖于document.readyState，但我建议观察页面加载的最后一个元素。您可以在加载最后一个元素的基础上进行进一步的处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Although document.readyState works most of the time, rather than relying on document.readyState, I would suggest observing which element on the page loads last. You can base the further processing on the loading of that final element

blocks|key|282905|text|和以前的回答一样，使用静态的“睡眠”不是个好主意。WebDriver等待(.)应该是你最好的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282906|但是，您需要对条件格外小心，因为有些元素以不同的顺序加载。在我的例子中，询问JS带来的结果是否已经就绪:)执行验证的方法：|282907|+return+((string)Driver.ExecuteScript("return+document.readyState")).Equals("complete");|code-block|syntax|javascript|282908|当然，驱动程序类是原始WebDriver驱动程序的包装器，要执行我正在使用的脚本：|282909|+public+object+ExecuteScript(string+javascriptCode,+params+object[]+args)
++++++++{
++++++++++++return+((IJavaScriptExecutor)DriverInstanceInstance).ExecuteScript(javascriptCode,+args);
++++++++}|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|P|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|R|8|@]|9|@]|A|$G|H]]]|M|$]]

As in previous responses, using static "sleeps" is not good idea. WebDriver Wait(...) should be best option for you.

However you need to be extra careful about the condition, as some elements are loading in different order. In my case bests results came with asking JS is everything is in place already :) Method that perform validation:

<pre><code> return ((string)Driver.ExecuteScript("return document.readyState")).Equals("complete");
</code></pre>

Of course Driver class is a wrapper around original WebDriver's driver and to execute script I'm using:

<pre><code> public object ExecuteScript(string javascriptCode, params object[] args)
 {
 return ((IJavaScriptExecutor)DriverInstanceInstance).ExecuteScript(javascriptCode, args);
 }
</code></pre>

blocks|key|282959|text|我们在产品中也遇到了这个问题，因为我们使用Dojo的过程更加复杂，并且在就绪状态完全更改之后执行Javascript代码。因此，我们在onload+Javascript完成后调用了一小部分Javascript代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282960|++++/**
+++++*+Sets+the+focus+on+a+field
+++++*/
++++setFocus+:+function(focusedElement,+defaultFocusGainedDivId)+{
++++++++//+timeout+needed+for+IE+to+work
++++++++setTimeout(function()+{
++++++++++++focusedElement.focus();
++++++++++++if+(+typeof+(focusedElement.select)+!==+"undefined")+{
++++++++++++++++//+select+a+value+in+the+text+inputs
++++++++++++++++//+only+(no+combobox).
++++++++++++++++focusedElement.select();
++++++++++++}

++++++++++++if(!defaultFocusGainedDivId)+{
++++++++++++++++defaultFocusGainedDivId+=+"defaultFocusGainedDiv";
++++++++++++}

++++++++++++domConstruct.create("div",+{"id":+defaultFocusGainedDivId,++"class":+"u-display-none"+},+win.body());

++++++++},+300,+focusedElement);
++++}|code-block|syntax|javascript|282961|然后，在Selenium端，我们有在加载新页面时调用的代码：|282962|private+static+By+defaultFocusGainedBy+=+By.cssSelector("div#defaultFocusGainedDiv.u-display-none");


/**
+*+Waits+for+5+seconds+for+a+div+with+id='defaultFocusGainedDiv'+and+css
+*+class='focusGained'.+This+div+is+added+after+the+focus+is+set+to+a+page's
+*+default+control+using+js/utils/CommonUtils.js'+setFocus()+function.
+*+
+*/
public+static+void+waitForPageFocusGained()+{
++++wdWait.until(ExpectedConditions.presenceOfElementLocated(defaultFocusGainedBy));
}|282963|这在很大程度上解决了这个问题，尽管您确实需要遵守规则才能继续使用这两个代码段。|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|O|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|R|8|@]|9|@]|A|$]]]|M|$]]

We faced this issue in our product too, with the added complication that we're using Dojo and as such have Javascript code that executes after the readystate complete change. Because of this, we have a small piece of Javascript code that we call after the onload Javascript has finished:

<pre><code> /**
 * Sets the focus on a field
 */
 setFocus : function(focusedElement, defaultFocusGainedDivId) {
 // timeout needed for IE to work
 setTimeout(function() {
 focusedElement.focus();
 if ( typeof (focusedElement.select) !== "undefined") {
 // select a value in the text inputs
 // only (no combobox).
 focusedElement.select();
 }

 if(!defaultFocusGainedDivId) {
 defaultFocusGainedDivId = "defaultFocusGainedDiv";
 }

 domConstruct.create("div", {"id": defaultFocusGainedDivId, "class": "u-display-none" }, win.body());

 }, 300, focusedElement);
 }
</code></pre>

Then on the Selenium end, we have this code that we call when loading a new page:

<pre><code>private static By defaultFocusGainedBy = By.cssSelector("div#defaultFocusGainedDiv.u-display-none");


/**
 * Waits for 5 seconds for a div with id='defaultFocusGainedDiv' and css
 * class='focusGained'. This div is added after the focus is set to a page's
 * default control using js/utils/CommonUtils.js' setFocus() function.
 * 
 */
public static void waitForPageFocusGained() {
 wdWait.until(ExpectedConditions.presenceOfElementLocated(defaultFocusGainedBy));
}
</code></pre>

This mostly fixes this issue, although you do need to have the discipline to keep using both snippets.

blocks|key|2117123|text|synchronized(driver)+{
++++++driver.wait(4000);
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|entityMap^0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$B|C]]]|D|$]]

<pre><code>synchronized(driver) {
 driver.wait(4000);
}
</code></pre>

I run nearly 30-40 test cases twice a day. And everytime some test case fails due to page load time. Infact i have explicitly mentioned <code>Thread.sleep("2000");</code> wherever i feel it takes more time to load. But still some 5-6 testCases fails. How can i make my selenium to wait until the page loads ?? And what would the below code do ?
<code>driver.manage().timeouts().implicitlyWait(4000, TimeUnit.SECONDS);</code> 
Will it wait for 4 seconds everytime or it sets the maximum time limit to 4 secs . I even tried this but it really slowed my test execution. I need some help.

Selenium test case fails due to page load time

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我每天运行近30-40个测试用例两次。而且每次一些测试用例由于页面加载时间而失败。事实上，我已经明确地提到了Thread.sleep("2000");，无论我觉得加载它需要更多的时间。但仍有5-6 testCases失败.我如何使我的硒等待直到页面加载？下面的代码会做什么呢？driver.manage().timeouts().implicitlyWait(4000, TimeUnit.SECON

问Selenium测试用例由于页面加载时间而失败
EN

回答 11

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Selenium测试用例由于页面加载时间而失败EN

回答 11

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Selenium测试用例由于页面加载时间而失败
EN