•  
     
    story #11314 Update step status for a test execution via REST
Summary
Empty
Update step status for a test execution via REST
Empty
Introduce PATCH testmanagement_executions/:id in order to update the status of a step:
{ "steps": [ { "id": <id>, "status": "passed" } ] }

This new status should be reflected in GET testmanagement_executions/:id and GET testmanagement_campaigns/:id/testmanagement_executions (add same "steps" in representation)

PUT testmanagement_executions/:id is not impacted (at least reject request if "steps" is part of the body, or implement update of steps if enough time)

Rules when step status is updated:
* if all steps are "passed", then the execution status switches automatically to passed
* if at least one step is "failed", then the execution status switches automatically to failed
* if at least one step is "blocked", then the execution status switches automatically to blocked
* if at least one step is "notrun", then the execution status switches automatically to notrun
Empty
Empty
Status
Empty
Canceled
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#11314
Nicolas Terray (nterray)
2018-06-19 21:45
2018-03-23 14:38
4389

References
Referencing story #11314

Follow-ups

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from Ready (stalled) to Canceled
  • Category set to