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

CaseRun.status not correctly mapped #184

Closed
sgrognard opened this Issue Jan 18, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@sgrognard

sgrognard commented Jan 18, 2018

Description of problem

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"

Component (web, API, etc)

tcms_api and web application

Version or commit hash (if applicable)

2fdb210

Steps to Reproduce

CaseRun().status = Status("FAILED")
CaseRun().update()

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment