Enable jasmine's stopSpecOnExpectationFailure feature for protractor

[machtyn]

(See also: http://stackoverflow.com/questions/37334069/protractor-jasmine-and-stopping-test-on-first-fail )

Jasmine 2.3.0 added an option stopSpecOnExpectationFailure that when set to true will stop a test on the first failure. However, attempting to set this option with jasmineNodeOpts failed.

/*
 * conf.js
 */
exports.config = {
    framework: 'jasmine',
    specs: ['search-spec.js'],
    useAllAngular2AppRoots: true,
    jasmineNodeOpts: {
        stopSpecOnExpectationFailure: true
    }
};

Additional information from user alecxe:

From what I see in the protractor and jasmine-npm (the jasmine runner that protractor uses) source code, it is not as simple as adding the stopSpecOnExpectationFailure or stopOnFailure jasmine node option to the configuration. There has to be changes applied to protractor to support the new stopSpecOnExpectationFailure jasmine node option. Please create an issue/feature request in Protractor issue tracker.

I've also tried to call the throwOnExpectationFailure function, set the stopSpecOnExpectationFailure value throw jasmine.getEnv() in onPrepare() but none of that worked. Perhaps, I am missing something and there is a way to enable the setting.

[harsha509]

Is there an ETA for this ?

[harsha509]

Hi @mgiambalvo ,
Is this feature included in the new version (4.0.0) , if yes pleases provide any documentation link.

Thanks in advance.

[juliemr]

It's non-trivial to add Protractor support for stopSpecOnExpectationFailure because it doesn't work with asynchronous tests. You can see this with plain old Jasmine and a test that looks like:

describe('async foo', function() {
  it('should bar', function(done) {
    setTimeout(function() {
      expect(1).toEqual(2);
    }, 10);
  });
});

You will see that instead of completing nicely, this tests will error without giving the reporter a chance to complete or letting the test shut down nicely.

We could, potentially, set up a global handler for uncaught exceptions and try to parse out when one is coming from Jasmine, but I'm very hesitant to add this infrastructure for one specific framework, especially since I wonder if Jasmine will be changing its support in the future.

I filed an issue with Jasmine at jasmine/jasmine#1213, let's see if there's an update there. Putting this in the 'blocked' milestone for now.