Nightwatch: Checking a Checkbox

[richard-flosi]

Is click() the right way to check a checkbox. It doesn't seem to be working for me. Please advise.

[davidlinse]

Would you mind looking at the api-docs ..

[richard-flosi]

I had to do .execute("$('" + selector + "').click();"); to get this to work.
Ideally .click() or .setValue() would work.

[nickcolley]

If this is a legit bug I wouldn't close it?

[richard-flosi]

As far as I can tell it is a legit bug, but it's unclear what is expected to work.

[beatfactor]

It's not a bug. it's something that concerns Selenium not something which
can be fixed in Nightwatch.

On Thu, Aug 28, 2014 at 12:29 AM, richard-flosi [email protected]
wrote:

As far as I can tell it is a legit bug, but it's unclear what is expected
to work.

—
Reply to this email directly or view it on GitHub
https://github.com/beatfactor/nightwatch/issues/249#issuecomment-53650137
.

[davidlinse]

@richard-flosi what about this ?

module.exports = {
  tags: ['checkbox'],

  'Demo test select a checkbox' : function (client) {
    client
      .url('your-domain.tld')
      .verify.visible('input[id="your_checkbox"]', 'Checkbox is visible')
      .click('input[id="your_checkbox"]')
      .pause(1000)
      .element('id', 'your_checkbox', function(response) {
        client.assert.ok(response.value.ELEMENT, 'Checkbox response is OK');
        client.elementIdSelected(response.value.ELEMENT, function(result){
          client.verify.ok(result.value, 'Checkbox is selected');
        });
      })
      .end();
  }
};

The above test runs fine for me.. (with replaced url of course ;)

Select-checkbox Test Suite
==========================

Running:  Demo test select a checkbox 

✔  Testing if element <input[id="your_checkbox"]> is visible.
✔  Assertion passed: Checkbox response is OK
✔  Assertion passed: Checkbox is selected

OK. 3 total assertions passed. (5571 ms)

regards
~david

[richard-flosi]

I was having an issue with a selector like input[name="foo"][value="1"] which selenium doesn't seem to like. I think it is unlikely that there will be an id on every checkbox. When I get a chance, I'll play with the selector again. I think something like input[name="foo"]:nth-child(1) might work, but that is far less elegant.

For comparison, webdriverio addresses the issue by injecting a click event: https://github.com/webdriverio/webdriverio/blob/f3de02f3c29cd0aa933979b26ca80b70609031c9/lib/helpers/click.js

[davidlinse]

indeed, this is some kind of 'issue' .

but just to make you know.
iirc the selenium docs say,
working with "id"s is actually THE way to go or at least the/their
preferred method of finding elements..

~david

[lacymorrow]

.click() seems to be working properly for me

[nickcolley]

Had similar problems to this with PhantomJS and changing the selector fixes it. No idea why.

[richard-flosi]

In general I've run into problems if my selector matches more than one item. Make sure you selector only matches one item and things tend to work. When they don't I use execute().