Test Name |
Description |
Status |
Duration |
Test: Step1-CreateNewAdverseEvent |
Create a new AdverseEvent in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created AdverseEvent resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step1-CreateNewAdverseEvent |
Create a new AdverseEvent in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created AdverseEvent resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step2-ReadAdverseEvent |
Read the AdverseEvent in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found AdverseEvent resource in JSON format. |
Failed |
|
Test: Step2-ReadAdverseEvent |
Read the AdverseEvent in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found AdverseEvent resource in JSON format. |
Failed |
|
|
Test: Step3-UpdateAdverseEvent |
Update the AdverseEvent created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated AdverseEvent resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step3-UpdateAdverseEvent |
Update the AdverseEvent created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated AdverseEvent resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step4-AdverseEventHistoryInstance |
Retrieve the updated AdverseEvent 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 AdverseEvent. |
Failed |
|
Test: Step4-AdverseEventHistoryInstance |
Retrieve the updated AdverseEvent 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 AdverseEvent. |
Failed |
|
|
Test: Step5-AdverseEventVersionRead |
Retrieve a initially created version of a AdverseEvent instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated AdverseEvent 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-AdverseEventVersionRead |
Retrieve a initially created version of a AdverseEvent instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated AdverseEvent 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-AdverseEventSearchType |
Search for AdverseEvent resources in JSON format with a resource id equal to ${searchParamId}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the AdverseEvent. |
Failed |
|
Test: Step6-AdverseEventSearchType |
Search for AdverseEvent resources in JSON format with a resource id equal to ${searchParamId}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the AdverseEvent. |
Failed |
|
|
Test: Step7-AdverseEventDelete |
Delete a AdverseEvent 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-AdverseEventDelete |
Delete a AdverseEvent 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 |
|
|