sync skip; aborting execution error thrown when this.skip() inside function

[przemek-rzedkowski]

Current behavior

Scenarios skipped with use of "@Focus" annotation generates a bug as seen on screenshot:

Focused scenario(s) run(s) correctly. It happened shortly after upgrading cypress to v.6.4.0 (I was using 6.3.0 before). Also I am using cypress-cucumber-preprocessor v.4.0.0. Problem disappears while running tests without annotation.
It's my first bug here so if you need any additional info please let me know, I will gladly provide :)

Desired behavior

It should simply run focused scenario(s) and skip the rest of them without failing .

Versions

Cypress v.6.4.0
cypress-cucumber-preprocessor v.4.0.0

[dthisner]

I have the same issue, example project can be located here that reproduces the issue: https://github.com/dthisner/cypressIssue
Issue logged at the cucumber-preprocess repo: badeball/cypress-cucumber-preprocessor#503

[jennifer-shehane]

As mentioned previously in the cucumber project, this can be reproduced solely in Cypress using the following code:

it("should work", function () {
  cy.then(() => this.skip()); // throws "sync skip; aborting execution"
});

This is sync skip; aborting execution error is being thrown from Mocha here: https://mochajs.org/api/runnable.js.html

/**
 * Halt and mark as pending.
 *
 * @memberof Mocha.Runnable
 * @public
 */
Runnable.prototype.skip = function() {
  this.pending = true;
  throw new Pending('sync skip; aborting execution');
};

I guess we're not handling this correctly in this case. This seems to have always errored in this case.

[vishnuprabhu-95]

I am facing same issue!

[bennymeade]

Same issue for me, to avoid this issue I had to roll back to:
"cypress": "^6.3.0",
"cypress-cucumber-preprocessor": "^4.0.0",

[damsorian]

Same issue for me, to avoid this issue I had to roll back to:
"cypress": "^6.3.0",

The problem seems to be in the 6.4.0 version, the 6.3.0. works as expected

[przemek-rzedkowski]

problem seems to be solved in v. 6.5.0

[narayananpalani]

Used 6.5.0 this morning and I got the same error when running tags in my repo.

[ataul821]

I see the same issue in 6.5.0 as well.