Serenity BDD Report
Report generated 23-03-2026 09:41

Read Information From A Resource Of Type Condition With Status "Resolved" (@condition-Read-Resolved)

  Mandatory   Basis   1 To 10 Seconds (Duration)   Stufe5

Read and Validate resolved Condition by its ID
Steps Outcome
When Get FHIR resource at "http://fhirserver/Condition/${data.condition-read-resolved-id}" with content type "xml"
SUCCESS 480ms
And FHIR current response body is a valid isik5 resource and conforms to profile "https://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnose"
SUCCESS 1s 675ms
And resource has ID "Condition-Read-Resolved-Example" with error message "The ID does not match the expected value"
SUCCESS 216ms
And FHIR current response body evaluates the FHIRPath "code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/icd-10-gm' and code = 'M17.0' and version = '2026.0.0').exists()" with error message 'The Condition code is missing or a required value is absent'
SUCCESS 215ms
And element "subject" references resource with ID "Patient-Read-Example" with error message "The referenced patient does not match the expected value"
SUCCESS 219ms
And FHIR current response body evaluates the FHIRPath "clinicalStatus.coding.where(system = 'http://terminology.hl7.org/CodeSystem/condition-clinical' and code = 'resolved').exists()" with error message "The Clinical status does not have the value 'resolved'"
SUCCESS 218ms
And FHIR current response body evaluates the FHIRPath 'recordedDate.toString().contains("2025-12-23")' with error message 'The resource does not contain the expected Documentation date'
SUCCESS 221ms
And FHIR current response body evaluates the FHIRPath 'note.text = "Illness resolved"' with error message 'The note does not match the expected value'
SUCCESS 219ms
And FHIR current response body evaluates the FHIRPath "bodySite.coding.where(system = 'http://snomed.info/sct' and version = 'http://snomed.info/sct/11000274103/version/20251115' and code = '49076000').exists()" with error message 'The body site code does not match the expected value'
SUCCESS 211ms
And TGR the custom failure message is set to "The end date does not contain the expected value"
SUCCESS 212ms
And TGR current response with attribute "$.body.Condition.abatementDateTime.value" matches "2026-01-07"
SUCCESS 214ms
And TGR the custom failure message is set to "The start date does not contain the expected value"
SUCCESS 218ms
And TGR current response with attribute "$.body.Condition.onsetDateTime.value" matches "2025-12-20"
SUCCESS 218ms
And TGR clear the custom failure message
SUCCESS 221ms
SUCCESS 4.77s
Serenity BDD version 4.3.2