Request : Support for non-callback usage about node-saucelabs HOT 5 CLOSED

hi @mekdev , I'm not quite sure why you wouldn't ever want to know if the call to saucelabs succeeded or not?

from node-saucelabs.

@mekdev if I don't hear back from you I'll close this issue in a couple of days

from node-saucelabs.

@mekdev @danjenkins Looks like the api supports callbacks and mocha allows callbacks with done. Here is a basic example

describe('Mocha tests', function () {
    var SauceLabs = require('saucelabs');
    var sauce;

    beforeEach(function () {
        var config = {
            username: process.env.SAUCE_USERNAME,
            password: process.env.SAUCE_ACCESS_KEY
        };

        sauce  = new SauceLabs(config);
    });

    afterEach(function () {
        sauce  = null;
    });

    it('should pass done callback for mocha', function (done) {
        sauce.getJobs(done);
    });

});

from node-saucelabs.

Hi guys,

Sorry for the delay, my intention wasn't to iqnore errors when omitting callbacks.
I was merely looking for a sync-like behavior (java/ruby) that would just block execution and throw error.

Our test pattern heavily uses co and the mocha promise manager from https://github.com/SeleniumHQ/selenium/wiki/WebDriverJs and we omit mocha done entirely.

The reason I requested this in the beginning is that I wanted to maintain our non-callback usage structure in our tests. Since then we have found our way around this by implementing our owner reporter and the tests looks alot cleaner now.

Please feel free to resolve as not fixed.

from node-saucelabs.

Great, thank you @mekdev !

from node-saucelabs.