-
Notifications
You must be signed in to change notification settings - Fork 25
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
Comments
Hi there oh ok, thank you so much for letting me know |
As a temporary solution, simply change the TestData constructor. @VoorheesM #39 |
Having same issue "Could not send list of TestRail results: 400 Bad Request >> Field :results.elapsed is not in a valid time span format." |
Hi there has been fixed with 2.8.1, also current dev-master has a fix for the broken screenshots (which also changed in cypress 13 haha) |
hi there
thank you so much
yeah theres a new case
somehow NANs is a value inside
so i updated to allow the check if the field doesnt even exist in cypress. but in ur case it exists but with an invalid value
i guess thats maybe only with a special combination in any way
i can fix that. shouldnt be hard
thx for ur help on that :)
|
should work now, |
Hi thanks for reporting this I've found indeed a scenario with your description, 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 |
hi, we have tested this fix and it work great 👌 |
perfect release will come soon...fixing something else and then :) |
released with 2.10.0 |
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
The text was updated successfully, but these errors were encountered: