With test_runner mocha, describe.only and it.only not excluding other tests

[kentendo]

.only() does not seem to be working. The 'has button one' and 'had button two' tests both run although 'has button one' should be run exclusively.

describe('my page', () => {
  describe.only('my buttons', () => {
    it.only('has button one', (client) => {
      client
        .url('http://localhost:3000')
        .expect.element('#one').to.be.present.before(1000);
    });
    it('has button two', (client) => {
      client
        .url('http://localhost:3000')
        .expect.element('#two').to.be.present.before(1000);
    });
  });
  describe('other buttons', () => {
    it('has button three', (client) => {
      client
        .url('http://localhost:3000')
        .expect.element('#three').to.be.present.before(1000);
    });
  });
});

Node Version: 6.9.5
Nightwatch Version: 0.9.14
Mac OS: 10.12.2
Chrome: 57

[ocmyhome]

I have this same problem!

[mrjamesriley]

This issue has only just appeared in the latest version of Nightwatch (0.9.14).
As a temporary solution, I'd recommend downgrading to version 0.9.13.

---

I'm not familiar enough with the codebase yet to see what's happening here.
But some pointers to help narrow down the issue:

.only( ) is not working with Nightwatch v0.9.14
But it is working with the version just before: v0.9.13

Nightwatch v0.9.14 depends on mocha-nightwatch 3.2.1
where as Nightwatch v0.9.13 depends on mocha-nightwatch 2.2.9

Mocha-nightwatch 3.2.1 merged Mocha 3.2.0
Mocha-nightwatch 2.2.9 is based on Mocha 2.2.5

It seems the issue here is that version 3 of Mocha brought about significant changes, for which the overriden Runner.js or Runnable.js of Mocha-nightwatch will need to be updated to reflect this, to bring back support for only().

[beatfactor]

I'll look into it and post a fix soon, sorry for the inconvenience.

[beatfactor]

Should be fixed in v0.9.15.