Test Name |
Description |
Status |
Duration |
Test: Step1-CreateNewProcedure |
Create a new Procedure in JSON format where the server assigns the resource id. The expected response code is 201 (Created) with a content of either the created Procedure resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step1-CreateNewProcedure |
Create a new Procedure in JSON format where the server assigns the resource id. The expected response code is 201 (Created) with a content of either the created Procedure resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step2-ReadProcedure |
Read the Procedure in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found Procedure resource in JSON format. |
Failed |
|
Test: Step2-ReadProcedure |
Read the Procedure in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found Procedure resource in JSON format. |
Failed |
|
|
Test: Step3-UpdateProcedure |
Update the Procedure created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated Procedure resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step3-UpdateProcedure |
Update the Procedure created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated Procedure resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step4-ProcedureHistoryInstance |
Retrieve the updated Procedure instance's history in JSON format. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the created and updated versions of the Procedure. |
Failed |
|
Test: Step4-ProcedureHistoryInstance |
Retrieve the updated Procedure instance's history in JSON format. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the created and updated versions of the Procedure. |
Failed |
|
|
Test: Step5-ProcedureVersionRead |
Retrieve a initially created version of a Procedure instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated Procedure resource in JSON format; if versioning is not supported, a 404 (Not Found) with an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step5-ProcedureVersionRead |
Retrieve a initially created version of a Procedure instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated Procedure resource in JSON format; if versioning is not supported, a 404 (Not Found) with an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step6-ProcedureSearchType |
Search for Procedure resources in JSON format with an identifier equal to ${searchParamIdentifier}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the Procedure. |
Failed |
|
Test: Step6-ProcedureSearchType |
Search for Procedure resources in JSON format with an identifier equal to ${searchParamIdentifier}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the Procedure. |
Failed |
|
|
Test: Step7-ProcedureDelete |
Delete a Procedure instance in JSON format. The expected response is either a 200 (OK) with an optional OperationOutcome in JSON format or 204 (No Content) and the content is empty; i.e. no content. |
Failed |
|
Test: Step7-ProcedureDelete |
Delete a Procedure instance in JSON format. The expected response is either a 200 (OK) with an optional OperationOutcome in JSON format or 204 (No Content) and the content is empty; i.e. no content. |
Failed |
|
|