Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Proper handling of alerts and prompts is still <a href="http://code.google.com/p/selenium/issues/detail?id=27" rel="nofollow noreferrer">being worked on</a> in WebDriver, but a common workaround is to overwrite the window functions using execute_script(), i.e.</p> <pre><code>browser.execute_script("window.alert = function(msg) { window.lastAlert = msg; }") browser.button(:id =&gt; "trigger-alert").click browser.execute_script("return window.lastAlert") #=&gt; "the message" </code></pre> <p>Since I'd like to avoid a bunch of monkey patches floating around (a common problem in the Watir community), I've added some <a href="http://github.com/jarib/watir-webdriver/commit/8fd5fd2a35c252fe4b72d401a655b01abb16b916" rel="nofollow noreferrer">helper methods</a> as an optional require - after the next release you should be able to do:</p> <pre><code>require "watir-webdriver/extensions/alerts" browser.alert do browser.button(:id =&gt; "alert").click end #=&gt; "the alert message" browser.confirm(true) do browser.button(:id =&gt; "confirm").click end #=&gt; "the confirm message" browser.prompt("returned value") do browser.button(:id =&gt; "prompt").click end #=&gt; { :message =&gt; "foo", :default =&gt; "bar" } </code></pre> <p>Note that this is temporary and the API may be removed in the future when the issue is resolved in WebDriver.</p> <p>UPDATE:</p> <p>Proper alert handling is now implemented. The above example would now be done like this:</p> <pre><code>browser.button(:id =&gt; "alert").click browser.alert.ok browser.button(:id =&gt; "confirm").click browser.alert.ok # or browser.alert.close browser.button(:id =&gt; "prompt").click alert = browser.alert alert.text #=&gt; "foo" alert.ok </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAlert box in Waitr Webdriver
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjarib
    1. USjarib
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI had an error using browser.alert and I fixed it with a hack, but you might want to had a look: http://gist.github.com/569969
      singulars
      1. PO
      1. USrtacconi
    2. COThe current behaviour is correct - if the button doesn't exist, it should raise an error. The idea is that you will write your own code in the block that will trigger the alert.
      singulars
      1. PO
      1. USjarib
    3. COSorry, I was calling it in the wrong place. However I tried your code but does not click any alert: assert_exists': unable to locate element, using {:value=>"OK", :tag_name=>"button"}
      singulars
      1. PO
      1. USrtacconi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload