You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using nightwatch with mocha, my test function look like this
it('uses BDD to run the Google simple test',function(browser){browser.url('http://google.com').expect.element('body').to.be.present.before(1000);browser.setValue('input[type=text]',['nightwatch',browser.Keys.ENTER]).pause(1000).assert.containsText('#main','Night Watch');});
(More detail about using mocha with nightwatch is here)
When I check with eslint, it says error Expected "browser" callback to be handled mocha/handle-done-callback
Mocha always expects the done callback parameter to be the first argument. The behavior of injecting the browser parameter is added by nightwatch and is not compatible with the default behavior of mocha.
That’s being said, I would be open for a change proposal that solves this kind of issues in a generic way (i.e. not nightwatch specific). Maybe something like adding a configuration option that allows you to specify the expected argument position.
I am using nightwatch with mocha, my test function look like this
(More detail about using mocha with nightwatch is here)
When I check with eslint, it says
error Expected "browser" callback to be handled mocha/handle-done-callback
I am using
The checker thinks
browser
isdone
callback, but it's not.The text was updated successfully, but these errors were encountered: