blocks|key|3589690|text|如果您的AJAX调用导致DOM更改，Capybara将等待您这样做|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589691|page.should+have_selector?("some+selector")|code-block|syntax|javascript|3589692|它是一个故意的Capybara特性，它等待(直到Capybara.default_wait_time)+have_selector?和相关方法为真。|offset|length|style|CODE|3589693|如果AJAX调用没有导致DOM更改，就无法使用Capybara在浏览器端等待更改。您也许能够在Javascript中检测到AJAX调用何时完成，并以某种方式将其传递给Capybara，但这将使您的测试和实现紧密耦合。在这种情况下，一种常见的方法是等待AJAX调用的服务器端效果(创建、更新或删除模型对象、发送电子邮件等)。发生的事情。由于Capybara看不到服务器端，您必须自己等待服务器端的更改。|3589694|在Capybara1中，您可以使用Capybara的wait_until等待服务器端的更改。wait_until已从Capybara2中删除。我在my+answer中向Why+does+adding+"sleep+1"+in+an+after+hook+cause+this+Rspec/Capybara+test+to+pass?发布了wait_until的实现|3589695|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/23555725/634576|1|https://stackoverflow.com/questions/23554882/why-does-adding-sleep-1-in-an-after-hook-cause-this-rspec-capybara-test-to-pas/23555725^0|0|0|O|Q|1G|E|0|0|Q|A|1A|A|4P|A|21|9|0|2C|2A|1|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@$I|19|J|1A|K|L]|$I|1B|J|1C|K|L]|$I|1D|J|1E|K|L]]|9|@$I|1F|J|1G|1|1H]|$I|1I|J|1J|1|1K]]|A|$]]|$1|Q|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

If your AJAX call results in a change to the DOM, Capybara will wait for it if you do

<pre><code>page.should have_selector?("some selector")
</code></pre>

It is an intentional Capybara feature that it waits (up to <code>Capybara.default_wait_time</code>) for <code>have_selector?</code> and related methods to be true.

If your AJAX call does not result in a change to the DOM, there's no way to wait for it on the browser side using Capybara. You might be able to detect when the AJAX call is complete in Javascript and somehow communicate that to Capybara, but that would couple your test and implementation rather tightly. A common approach in this case is to wait for the server-side effect of your AJAX call (creation or update or deletion of a model object, sending of an email, etc.) to take place. Since Capybara can't see the server side you have to wait for the server-side change yourself.

In Capybara 1 you can use Capybara's <code>wait_until</code> to wait for the server-side change. <code>wait_until</code> was removed from Capybara 2. I posted an implementation of <code>wait_until</code> in <a href="https://stackoverflow.com/a/23555725/634576">my answer</a> to <a href="https://stackoverflow.com/questions/23554882/why-does-adding-sleep-1-in-an-after-hook-cause-this-rspec-capybara-test-to-pas/23555725">Why does adding &quot;sleep 1&quot; in an after hook cause this Rspec/Capybara test to pass?</a>

blocks|key|3589701|text|可能是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589702|#+AJAX+BEGIN
++expect(page).to+have_selector('form#new_user_video+.submit+>+.throbber')
++expect(page).to_not+have_selector('form#new_user_video+.submit+>+.throbber')
++#+AJAX+END|code-block|syntax|javascript|3589703|在js代码中手动设置'ajax:send‘(追加throbber)和'ajax:success’(删除throbber)。这样，您将能够知道请求何时完成。|3589704|并且您应该为ajax设置足够的时间来完成：|3589705|Capybara.default_max_wait_time+=+5|3589706|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Maybe something like this:
<pre><code># AJAX BEGIN
 expect(page).to have_selector('form#new_user_video .submit &gt; .throbber')
 expect(page).to_not have_selector('form#new_user_video .submit &gt; .throbber')
 # AJAX END
</code></pre>
Manually in your js code set 'ajax:send' (append throbber) and 'ajax:success' (remove throbber). This way you'll be able to know when request is finished.
And you should set enough time for ajax to complete:
<pre><code>Capybara.default_max_wait_time = 5
</code></pre>

blocks|key|3589738|text|我真的不需要期望，因为它不是我需要测试的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589739|这对我很有效：|3589740|page.has_css?('.my-selector')
#+or
page.has_content?('Some+text+on+the+page')

#+continue+with+test|code-block|syntax|javascript|3589741|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I didn't really need the expectation as it wasn't what I needed to test.
This worked for me:
<pre><code>page.has_css?('.my-selector')
# or
page.has_content?('Some text on the page')

# continue with test
</code></pre>

The capybara method, <code>wait_until</code> doesn't seems to work for capybara-webkit. Is there any alternate solution for that, or any Javascript implementations?

Intentionally need some replacement for <code>sleep</code>, e.g. <code>sleep 2</code>.

<img src="https://i.stack.imgur.com/WHM0t.png" alt="enter image description here">

How to wait till an element appears after an AJAX call using capybara-webkit?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

水豚的方法，wait_until似乎不适用于水豚-webkit。有没有其他的解决方案，或者Javascript的实现？我有意需要一些sleep的替代品，例如sleep 2。​​

问如何使用capybara-webkit在AJAX调用后等待一个元素出现？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用capybara-webkit在AJAX调用后等待一个元素出现？EN