We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When modifying the status of a CaseRun using tcms_api, this is not correctly reflected in the web application.
E.g.:
CaseRun().status = Status("FAILED") CaseRun().update()
When checking the status of in the web application, it is shown as "PAUSED". CaseRun().status is still correctly set to Status("FAILED") however.
This appears to be the current "mapping":
"FAILED" => "PAUSED" "PASSED" => "RUNNING" "PAUSED" => "FAILED" "RUNNING" => "PASSED" "BLOCKED" => "BLOCKED" "ERROR" => "ERROR"
tcms_api and web application
2fdb210
Status of this CaseRun in the web application is shown as "FAILED"
Status of this CaseRun in the web application is shown as "PAUSED"
The text was updated successfully, but these errors were encountered:
[api] Fix order of TestCaseRun statuses. Fixes #184
3674683
1800212
No branches or pull requests
Description of problem
When modifying the status of a CaseRun using tcms_api, this is not correctly reflected in the web application.
E.g.:
When checking the status of in the web application, it is shown as "PAUSED".
CaseRun().status is still correctly set to Status("FAILED") however.
This appears to be the current "mapping":
Component (web, API, etc)
tcms_api and web application
Version or commit hash (if applicable)
2fdb210
Steps to Reproduce
Actual results
Status of this CaseRun in the web application is shown as "FAILED"
Expected results
Status of this CaseRun in the web application is shown as "PAUSED"
The text was updated successfully, but these errors were encountered: