Test Name |
Description |
Status |
Duration |
Test: Step1-CreateNewSlot |
Create a new Slot in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created Slot resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step1-CreateNewSlot |
Create a new Slot in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created Slot resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step2-ReadSlot |
Read the Slot in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found Slot resource in JSON format. |
Failed |
|
Test: Step2-ReadSlot |
Read the Slot in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found Slot resource in JSON format. |
Failed |
|
|
Test: Step3-UpdateSlot |
Update the Slot created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated Slot resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step3-UpdateSlot |
Update the Slot created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated Slot resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step4-SlotHistoryInstance |
Retrieve the updated Slot 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 Slot. |
Failed |
|
Test: Step4-SlotHistoryInstance |
Retrieve the updated Slot 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 Slot. |
Failed |
|
|
Test: Step5-SlotVersionRead |
Retrieve a initially created version of a Slot instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated Slot 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-SlotVersionRead |
Retrieve a initially created version of a Slot instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated Slot 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-SlotSearchType |
Search for Slot 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 Slot. |
Failed |
|
Test: Step6-SlotSearchType |
Search for Slot 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 Slot. |
Failed |
|
|
Test: Step7-SlotDelete |
Delete a Slot 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-SlotDelete |
Delete a Slot 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 |
|
|