Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cypress 13.0, cannot upload results to test rail #38

Closed
VoorheesM opened this issue Aug 29, 2023 · 13 comments
Closed

Cypress 13.0, cannot upload results to test rail #38

VoorheesM opened this issue Aug 29, 2023 · 13 comments
Assignees
Labels
issue:bug Something isn't working Released

Comments

@VoorheesM
Copy link

when running a test the following message is desplayed:

#TestRail >> Sending case results to run R563: C135
Could not send list of TestRail results: 400 Bad Request >> Field :results.elapsed is not in a valid time span format.

this was not that case right before updating to cypress 13.0 so it looks like something was changed there causing this issue

@boxblinkracer
Copy link
Owner

Hi there

oh ok, thank you so much for letting me know
I'll upgrade our cypress project and give it a try

@boxblinkracer boxblinkracer added the issue:bug Something isn't working label Aug 30, 2023
@M4xymS
Copy link
Contributor

M4xymS commented Sep 5, 2023

As a temporary solution, simply change the TestData constructor. @VoorheesM #39

@harishigg
Copy link

Having same issue "Could not send list of TestRail results: 400 Bad Request >> Field :results.elapsed is not in a valid time span format."

@boxblinkracer
Copy link
Owner

Hi there

has been fixed with 2.8.1,
forgot to mention it here

also current dev-master has a fix for the broken screenshots (which also changed in cypress 13 haha)

@natalivoloshyn
Copy link

Hi there,
This issue is still reproducible on 2.8.2
We run tests using tag - so not all tests are launched. Previously results of Pending tests were not pushed to TestRail.
image

@boxblinkracer
Copy link
Owner

boxblinkracer commented Dec 29, 2023 via email

@boxblinkracer
Copy link
Owner

ok
I found it with a new jest test
pretty sure undefined happens, ill add a fix

Screenshot 2023-12-29 at 16 28 47

@boxblinkracer
Copy link
Owner

should work now,
can you give it a try with the latest dev-master
(please also note, axios has been updated, so you might need to reinstall node-modules if sth is weird)

@natalivoloshyn
Copy link

natalivoloshyn commented Jan 29, 2024

Hello,
Unfortunatelly this issue is still present if there are 3 and more tests
image

@boxblinkracer
Copy link
Owner

Hi

thanks for reporting this

I've found indeed a scenario with your description,
so in cypress 13, skipped tests have a duration of "0". Unfortunately because of a not-so-good-implicit if (data.duration) check, it went into checking attempt array from old Cypress <= v12...which of course didnt work either...so "NaN" was back as value

in the end a single jest-unit test was missing and showed the error

i've restructured it a bit more to cover more cases and its working now for me

can you check out dev-master and tell me if its working?

sorry for the inconvenience

@boxblinkracer boxblinkracer added In QA developed, in-review and ready for release once approved and removed Released labels Jan 30, 2024
@boxblinkracer boxblinkracer self-assigned this Jan 30, 2024
@natalivoloshyn
Copy link

dev-master

hi,

we have tested this fix and it work great 👌
Thank you very much for it.
we are waiting for the next release ❤️

@boxblinkracer
Copy link
Owner

perfect
thanks for the feedback

release will come soon...fixing something else and then :)

@boxblinkracer boxblinkracer added QA Approved (coming with next release) and removed In QA developed, in-review and ready for release once approved labels Feb 1, 2024
@boxblinkracer boxblinkracer reopened this Feb 1, 2024
@boxblinkracer
Copy link
Owner

released with 2.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue:bug Something isn't working Released
Projects
None yet
Development

No branches or pull requests

5 participants