NRL-1329 Make it even more formatted

Author: axelkrastek1-nhs

tests/producer-test-cases.md

@@ -9,8 +9,8 @@ update/supersede and delete pointers.
 
 ### **TC-P01 - Create happy path / success scenario**
 
-|**Step**|**Detailed instructions**|**Evidence required**|**Expected outcome**|
-|--------|-------------------------|---------------------|--------------------|
+| **Step** | **Detailed instructions** | **Evidence required** |**Expected outcome** |
+|----------|---------------------------|-----------------------|---------------------|
 | 1        | Authenticate as a valid organisation with a valid access token. | | |
 | 2        | Construct a new DocumentReference for the request body.<br> <ul> <li>Use test patient with NHS number 9876543210</li> <li>Type should reflect whichever type you plan on using in live, as agreed in IAG.</li> <li>All mandatory fields must be populated, and any other fields you plan to use in your live implementation should be populated as you intend to use them.</li> <li>Do not include a relatesTo section.</li> </ul> | Please include a copy of the request body as it was sent in. | Request body is a valid FHIR R4 DocumentReference that adheres to the additional constraints detailed in the API specification, as well as any other constraints mentioned in the compliance checklist. |
 | 3        | Send as a POST request to the /DocumentReference endpoint, along with headers specified in the API spec.<br> Audit logs should contain details of the request. | Save an extract or screenshot of the audit logs for this request in the appropriate folder. | Audit logs show:<br> <ul> <li>HTTP request body</li> <li>HTTP request URL</li> <li>HTTP verb</li> <li>ODS code of sender</li> <li>NHS number of patient</li> <li>Request date-time</li> <li>Request ID</li> <li>Correlation ID?</li> </ul> |
@@ -20,8 +20,8 @@ update/supersede and delete pointers.
 
 ### **TC-P02 - Read happy path / success scenario**
 
-|**Step**|**Detailed instructions**|**Evidence required**|**Expected outcome**|
-|--------|-------------------------|---------------------|--------------------|
+| **Step** | **Detailed instructions** | **Evidence required** |**Expected outcome** |
+|----------|---------------------------|-----------------------|---------------------|
 | 1        | Authenticate as a valid organisation with a valid access token. | | |
 | 3        | Send a GET request for the pointer created in TC-01 using the ID generated and recorded. | Save an extract or screenshot of the audit logs for this request in the appropriate folder.  | Audit logs show:<br> <ul> <li>HTTP request body</li> <li>HTTP request URL</li> <li>HTTP verb</li> <li>ODS code of sender</li> <li>NHS number of patient</li> <li>Request date-time</li> <li>Request ID</li> <li>Correlation ID?</li> </ul> |
 | 4        | View the pointer received in the response.                                               | Save an extract or screenshot of the audit logs for this response in the appropriate folder. | Audit logs show:<br> <ul> <li>HTTP response body (a DocumentReference)</li> <li>HTTP response code (200)</li> <li>Response datetime</li> <li>The pointer ID (found in the location header)</li> <li>Correlation ID?</li> </ul>             |
@@ -30,8 +30,8 @@ update/supersede and delete pointers.
 
 ### **TC-P03 - Supersede happy path / success scenario**
 
-|**Step**|**Instructions/ Guidance**|**Evidence required**|**Expected outcome**|
-|--------|--------------------------|---------------------|--------------------|
+| **Step** | **Instructions/ Guidance** | **Evidence required** | **Expected outcome** |
+|----------|----------------------------|-----------------------|----------------------|
 | 1        | Authenticate as a valid organisation with a valid access token. | | |
 | 2        | Construct a DocumentReference for the request body that will supersede the pointer created in TC01.<br> <ul> <li>Use the same request body as in TC01. NHS number, type and category must match.</li> <li>Populate the relatesTo section with the pointer ID generated in TC01 (found in the location header of the response).</li> </ul> | Please include a copy of the request body as it was sent in.                                 | Request body is a valid FHIR R4 DocumentReference that adheres to the additional constraints detailed in the API specification, as well as any other constraints mentioned in the compliance checklist. |
 | 3        | Send as a POST request to the /DocumentReference endpoint, along with headers specified in the API spec.<br> Audit logs should contain details of the request.  | Save an extract or screenshot of the audit logs for this request in the appropriate folder.  | Audit logs show:<br> <ul> <li>HTTP request body</li> <li>HTTP request URL</li> <li>HTTP verb</li> <li>ODS code of sender</li> <li>NHS number of patient</li> <li>Request date-time</li> <li>Request ID</li> <li>Correlation ID?</li> </ul> |
@@ -41,8 +41,8 @@ update/supersede and delete pointers.
 
 ### **TC-P04 - Search happy path / success scenario (multiple results)**
 
-|**Step**|**Detailed instructions**|**Evidence required**|**Expected outcome**|
-|--------|-------------------------|---------------------|--------------------|
+| **Step** | **Detailed instructions** | **Evidence required** |**Expected outcome** |
+|----------|---------------------------|-----------------------|---------------------|
 | 1        | Authenticate as a valid organisation with a valid access token.   | | |
 | 2a OR 2b | <ul> <li>Send a GET search request for all pointers using the NHS number.</li> <li>Send a POST search request for all pointers using the NHS number.</li> </ul> | Save an extract or screenshot of the audit logs for this request in the appropriate folder.  | Audit logs show:<br> <ul> <li>HTTP request body</li> <li>HTTP request URL</li> <li>HTTP verb</li> <li>ODS code of sender</li> <li>NHS number of patient</li> <li>Request date-time</li> <li>Request ID</li> <li>Correlation ID?</li> </ul> |
 | 3        | View the searchset bundle received in the response.<br> There should be at least TWO DocumentReferences; the one you created (and superseded) in the previous tests, and another one created by NRLF filled with example data. | Save an extract or screenshot of the audit logs for this response in the appropriate folder. | Audit logs show:<br> <ul> <li>HTTP response body (a DocumentReference)</li> <li>HTTP response code (200)</li> <li>Response datetime</li> <li>The pointer ID (found in the location header)</li> <li>Correlation ID?</li> </ul> |