Skip to content

NRL-1215 recreate reported bug as an integration test #769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
katebobyn-nhs wants to merge 1 commit into from
Closed

NRL-1215 recreate reported bug as an integration test #769

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 49 additions & 1 deletion tests/features/producer/createDocumentReference-failure.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@
# Invalid document reference - missing custodian identifier
# Invalid document reference - missing subject identifier
# Invalid document reference - invalid custodian system
# Invalid document reference - invalid subject system
# Invalid document reference - invalid relatesTo code
# Invalid document reference - invalid relatesTo target
# Invalid document reference - multiple type.coding
Expand Down Expand Up @@ -570,6 +569,55 @@ Feature: Producer - createDocumentReference - Failure Scenarios
}
"""

Scenario: NRL-1215 Bug report multiple content.attachment urls
Given the application 'DataShare' (ID 'z00z-y11y-x22x') is registered to access the API
And the organisation 'TSTCUS' is authorised to access pointer types:
| system | value |
| http://snomed.info/sct | 1363501000000100 |
| http://snomed.info/sct | 736253002 |
When producer 'TSTCUS' requests creation of a DocumentReference with default test values except 'content' is:
"""
"content": [
{
"attachment": {
"contentType": "application/pdf",
"language": "en-UK",
"url": "https://spine-proxy.national.ncrs.nhs.uk/https%3A%2F%2Fp1.nhs.uk%2FMentalhealthCrisisPlanReport1.pdf",
"url": "https://spine-proxy.national.ncrs.nhs.uk/https%3A%2F%2Fp1.nhs.uk%2FMentalhealthCrisisPlanReport2.pdf",
"title": "Mental health crisis plan report",
"creation": "2022-12-21T10:45:41+11:00"
},
"format": {
"system": "https://fhir.nhs.uk/England/CodeSystem/England-NRLFormatCode",
"code": "urn:nhs-ic:unstructured",
"display": "Unstructured document"
}
}
]
"""
Then the response status code is 400
And the response is an OperationOutcome with 1 issue
And the OperationOutcome contains the issue:
"""
{
"severity": "error",
"code": "value",
"details": {
"coding": [
{
"system": "https://fhir.nhs.uk/ValueSet/Spine-ErrorOrWarningCode-1",
"code": "INVALID_RESOURCE",
"display": "Invalid validation of resource"
}
]
},
"diagnostics": "Invalid practice setting coding: display Ophthalmology service does not match the expected display for 788002001 Practice Setting coding is bound to value set https://fhir.nhs.uk/England/ValueSet/England-PracticeSetting",
"expression": [
"context.practiceSetting.coding[0]"
]
}
"""

Scenario Outline: Invalid display value for type or category (imaging)
Given the application 'DataShare' (ID 'z00z-y11y-x22x') is registered to access the API
And the organisation 'ANGY1' is authorised to access pointer types:
Expand Down
Loading