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

Error in 2.8.1 "Could not send list of TestRail results: 400 Bad Request >> Field :results.status_id is not a valid status. " #41

Open
SimonasB88 opened this issue Sep 11, 2023 · 6 comments
Labels
issue:duplicate This issue or pull request already exists issue:question Further information is requested

Comments

@SimonasB88
Copy link

Not sure, if I am duplicating, but upgraded the extension, and now receiving:
image

image

@SimonasB88
Copy link
Author

SimonasB88 commented Sep 11, 2023

FYI, seems like if I leave the same test cases ID in the another run at the same time, and I change only the TestRail run ID on the other run, this error is shown on the 2nd parallel run only.

@boxblinkracer
Copy link
Owner

hi there

did you manipulate the status entries in testrail?

@boxblinkracer boxblinkracer added the issue:question Further information is requested label Oct 20, 2023
@yegs1995
Copy link

yegs1995 commented Feb 5, 2024

Hi @boxblinkracer I updated to version 2.10.0 and I'm getting the same issue. The error is because the CypressStatusConverter returns -1 when Cypress returns the skipped status
image

image

@boxblinkracer
Copy link
Owner

Hi

yes thats absolutely like it is
because the custom mapping is planned for the next release

2.10 fixes an elapsedTime bug with pending tests, and allows you to set "ignorePending" to true, which skips pending tests from being sent

then next feature, which is a main-feature is to introduce brand new mappings.
back then when i started the integration i did encapsualte the tests for the status conversion to be already flexible to be configured using settings...this will now come

because some people want something else for a specific Cypress status...and some might even have complete custom status values inside TestRail

i hope this helps :)

@boxblinkracer
Copy link
Owner

this will be the issue for it: #44

@boxblinkracer boxblinkracer added the issue:duplicate This issue or pull request already exists label Feb 5, 2024
@laerteneto
Copy link

laerteneto commented May 14, 2024

The same issue was observed in my test suite. Sometimes, I see this error and I don't know why, since all the tests are following the pattern ''C123456: + test case name'

I'm running the latest version and setting the ignorePeding flag as true, but the same issue continues to be observed in my runs.

Example 1:
image

Example 2:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue:duplicate This issue or pull request already exists issue:question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants