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