Support for alert(), confirm() and prompt() boxes?

[sigmaris]

Is there any way using the Mink API to, for example, click on the OK or Cancel buttons on a Javascript-generated confirm dialog box or fill in text in a dialog generated from prompt()? We're having trouble testing steps that require the user to confirm certain actions such as deleting objects, since the confirmation doesn't seem to succeed. FWIW we're using Mink 1.3.2 with the ZombieDriver.

[oleksiizozulenko]

I need this too.
I use Selenium2Driver.

[mekras]

For a test I implemented Selenium WebDriver "acceptAlert" method support here: ef33938. But I'm not sure that WebDriver-like interface will fit other drivers. With some help from Mink developers in this question I can try to implement alert support at least for WebDriver.

[damehta]

Looking forward for this issue resolution.

With php-SeleniumWebDriver I tried: $this->getSession()->accept_alert();
returned error: PHP Fatal error: Call to undefined method Behat\Mink\Session::accept_alert() in

[stof]

@damehta getSession() will not give you the selenium class. It gives you the Behat\Mink\Session class.

[damehta]

@mekras Do you know ETA for this issue resolution in the release? I hope ef33938 becomes available in upcoming release. Thanks so much for the fix.

[stof]

@damehta there is no pull request for this commit, so it has never been integrated as part of the official repo

[mekras]

@stof I can create a pull request but I'm not sure if my solution fits Mink architecture.

[blazarecki]

Hi, I find a solution to use alert(), confirm() and prompt() in Selenium2Driver
Link to my gist

[Spudley]

As per discussion on support forum (https://groups.google.com/forum/?fromgroups#!topic/behat/Cc6OcObVWnE), we are looking for a solution to this same issue, using Sahi.

Sahi itself supresses the browser's modal dialogs and simply replaces them with a JS function that returns the expected value.

The default return value for alert() and confirm() is true; if you want to test a negative response to confirm() then Sahi needs to be told about this prior to the confirm() being called. This is discussed here: http://sahi.co.in/w/_expectconfirm

This method of working means you can't simply write a script that says "click the cancel button"; you need to say "when the next confirm box appears, I want the cancel button to be clicked". This may not be the same way that other drivers would do it, but may affect the architecture decisions for writing a Mink method to support it.

[aik099]

A reincornation of this issue can be found in this PR: https://github.com/Behat/Mink/pull/356

[aik099]

Thinking more about a subject I think we might need to implement interface for setting expectations on upcoming alert/confirm/prompt dialogs similar to Sahi implementation. I know, that Selenium is much more powerful in that aspect, that it can click on alert/confirm/prompt even after it has appeared, but Sahi isn't.

Placing following Mink code right before triggering an action, that would cause alert/confirm/prompt to appear might solve the problem:

$session->expectDialog(Session::ALERT_DIALOG)->withText('dialog text here')->thenPressOK();
$session->expectDialog(Session::CONFIRM_DIALOG)->withText('dialog text here')->thenPressOK();
$session->expectDialog(Session::CONFIRM_DIALOG)->withText('dialog text here')->thenPressCancel();
$session->expectDialog(Session::PROMPT_DIALOG)->withText('dialog text here')->typeText('some text here')->thenPressOK();
$session->expectDialog(Session::PROMPT_DIALOG)->withText('dialog text here')->typeText('some text here')->thenPressCancel();

The withText and typeText methods are optional. This way you can set less/more detailed expectation for upcoming dialog. I suppose, that there can only be 1 dialog expectation at one time.

Problems with Selenium:

With Selenium we can't really set expectations on a dialog and we need to check if expectation is fulfilled after each driver command, which isn't very good. Also if somebody does this $session->getDriver()->getWDSession()->click(....), then we can't process dialog expectation.

Problems with Sahi

It seems, that with Sahi you can't really skip matching on dialog text part (see http://sahi.co.in/w/_expectConfirm), but maybe I'm wrong.

Overall problems

When dialog appears after an AJAX call we can't easily catch that in Selenium/Sahi, because test execution doesn't wait for ajax call to finish (unless we do a conditional wait call with check for an element, that would appear after ajax call has finished).

Any thoughts?

[aik099]

@stof , @everzet any thoughts about https://github.com/Behat/Mink/issues/158#issuecomment-27373068 ?

[stof]

I kinda like the the expectation based API. I'm not sure how this would work for the Behat integration though. But this is a separate topic IMO. @aik099 would you have some time to investigate whether it would work with the different JS drivers ?
I would like to hear what @everzet thinks about this API as well