Oleksandr Shevtsov

Hi @Sheth90 As #179 is resolved in v2.38.3, I think your case should also be fixed as well. Please check it on your end.

@Sheth90 That means your specific case was not covered or covered just partially thus requires further investigation. However, I can confirm that when I used `cypress-parallel` **sometimes** some of the...

@AndriiZhydkykh I am afraid, answer would be "no", as we define configuration in runtime, and at the start of the test we do not know the status yet. Probably it...

Currently blocked by https://github.com/Shelex/cypress-allure-plugin/issues/186

Hi Andrii, thank you for questions. Also thank you for using this plugin. I am glad it helped you. > Should I continue to expect support and updates for the...

Hi. That was implemented exactly as an attempt to fix "disappearing" tests due to names duplication https://github.com/Shelex/cypress-allure-plugin?tab=readme-ov-file#test-name-duplicates In case full title is still required for some reason, it could be...

I think the problem here is caused by test which is not attached to any suite and works just because cypress wraps everything in some "global" suite per file, however...

Hi @nthallap! There could be various reasons for that, and most common - when tests have same names accross suites then other test case is calculated as a retry in...

Hi @varshanharshank > This issue is happening often for random test cases. I have an example repo https://github.com/Shelex/cypress-allure-plugin-example where I am already checking that in case cypress crashes - the...

Hi @Smriti-Suhag Thank you for opening an issue. Due to publishing token expiration and missing option to regenerate new one I have forked plugin under my personal account: [Cypress Helper...