2

I added fail-fast to my cucumberOpts like below: 

cucumberOpts: {
  require: [
  conf.paths.e2e + '/utilities/hooks.js', 
  ],
  format: 'pretty',
  'fail-fast': true
  },

I have all my tests in a path like this: C:/tests/*.feature

I run my tests like this: protractor protractor.conf.js

This works fine as in it will stop the tests as soon as there's an error. But I'm having these tests run in a CI server like Bamboo and I was hoping to give rapid feedback while continuing to run the rest of the tests on faillure.

So if I have 4 tests in total, if the first test fails, I want to fail-fast on that first test then I want to continue running the other 3 tests/feature files.

What it is doing now, which I don't like, is it will fail as soon as one test fails and it will NOT run any of the other feature files.

Any idea ?

pelican
  • 5,846
  • 9
  • 43
  • 67

1 Answers1

0

I think that is a problem with the protractor 4 version.

Could you downgrade to version protractor 3.3.0 and check if it is working as expected?

Some issues are in protractor, cucumberjs and other repositories:

I will hope that they will fix the problem as soon as possible in next releases.

Adolfo Luzardo Cabrera
  • 595
  • 6
  • 14
  • Downgrading didn't work either; is it working for you at v3.3.0? Are the rest of your tests still running even after a previous test failed-fast? – pelican Sep 30 '16 at 13:51
  • Does anyone else have any ideas/clues I'm still struggling with not being able to run the rest of my other features after a previous feature failed with fail-fast = true; this is blocking proper reporting on our CI server and without that flag the e2e tests are taking a very long time even with multicapabilities (parallel) – pelican Sep 30 '16 at 13:52