Custom configuration for status mappings between Cypress and TestRail

[imutiara]

everytime I running by tags(e.g npx cypress run --env TAGS="@smoke"), the other feture file is finish with status pending and send to testrail as blocked

[boxblinkracer]

Hi

so this makes actually sense if you know the background...but please let me know your use case, so I can think of a solution

what should happen is....
when you prepare a testrail run with all tests...then you run cypress in filter mode...this should ensure that all tests are green or red...and the ones that are not executed should also be marked...these are marked as "blocked" for now as synonym for "not executed". but I just saw that there is also the option to revert back to "untested" which might be more appropriate

what do you think?
changing them to "untested" is better?

thank you

[natalivoloshyn]

Hi,
We also have this problem.
Could you please fix it in the same way as it was in the older version:
If launch tests run with any tag (like TAGS="@smoke") - all test results that have the status 'Pending' should not be sent to TestRail at all.
Pending here actually means that we are not interested in them because they were skipped intentionally.

Thank you!

[boxblinkracer]

Hi

thanks

I think i need to create a config, because different people want different things in that scenario over time

so I'll make sure to have everything possible, i think thats the only solution

[boxblinkracer]

Hi

so the latest dev-master already contains the first part.
The new variable "ignorePending" allows to configure if pending cypress tests should be sent to Cypress at all.

[natalivoloshyn]

"ignorePending"

thank you for this fix very much. For us, it works very well👌

[boxblinkracer]

perfect, thanks for the feedback, coming soon :)