Allure-results can't be created if "context.skip" or "describe.skip" is presented in suite body about cypress-allure-plugin HOT 6 CLOSED

@Seitar18 Thank you for opening issue.
Actually it is known one. I have no idea why Cypress after receiving mocha "pending" event (that happens when next test\suite should be skipped) and if there is no other tests\hooks left - just stops cypress runner and as a result no commands could be used, so results are not saved.

It will require proper investigation if this could be fixed or workaround found.
I assume empty after hook may work in case you don't have any hooks yet.

from cypress-allure-plugin.

@Shelex thank you for your answer.
Unfortunately we have many before hooks at those tests.
So, may be global after hook should help?

from cypress-allure-plugin.

@Shelex thank you for your answer.
Unfortunately we have many before hooks at those tests.
So, may be global after hook should help?

When I was debugging such issue it helped me. When any other executable is scheduled after skipped test - allure results writer is fine.

from cypress-allure-plugin.

@Shelex thank you for your answer.
Unfortunately we have many before hooks at those tests.
So, may be global after hook should help?

When I was debugging such issue it helped me. When any other executable is scheduled after skipped test - allure results writer is fine.

Thanks a lot[2]!
This call at support/index.js is solved this problem.
after(function () {
});

from cypress-allure-plugin.

@Seitar18 glad it helped!
However it should be addressed properly, so let's leave issue opened.

from cypress-allure-plugin.

Addressed in 2.6.0.

from cypress-allure-plugin.