Serenity BDD Report
Home > Requirements > Stufe5 > Basis > Testing search parameters against a resource of type condition (@condition-search)
Report generated 23-03-2026 09:41

Feature: Testing search parameters against a resource of type condition (@condition-search)

Scenarios

Given the Test Description: "The system under test MUST find a previously created resource when searched using the parameter and return it in the search results (SEARCH)."

Given the Preconditions: - The Condition-Read-Active test case must have been executed successfully beforehand.

When Get FHIR resource at "http://fhirserver/metadata" with content type "json"

And CapabilityStatement contains interaction "search-type" for resource "Condition"

And CapabilityStatement contains definition of search parameter "{searchParamValue}" of type "{searchParamType}" for resource "Condition"

Examples:

searchParamValuesearchParamType
_idtoken
_countnumber
patientreference
subjectreference
encounterreference
recorded-datedate
relatedreference

Examples:

searchParamValuesearchParamType
_tagtoken 
clinical-statustoken 
categorytoken 

When Get FHIR resource at "http://fhirserver/Condition/?_id=${data.condition-read-active-id}" with content type "xml"

And FHIR current response body is a valid CORE resource and conforms to profile "https://hl7.org/fhir/StructureDefinition/Bundle"

And response bundle contains resource with ID "${data.condition-read-active-id}" with error message "The requested Condition ${data.condition-read-active-id} is not contained in the response bundle"

When Get FHIR resource at "http://fhirserver/Condition/?_tag=${data.tag-system}%7C${data.tag-value}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(meta.tag.where(code='${data.tag-value}').exists())" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?_count" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'total } 0 and entry.resource.count() } 0' with error message 'No search results were found'

When Get FHIR resource at "http://fhirserver/Condition/?subject=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "subject" in all bundle resources references resource with ID "${data.patient-read-id}"

When Get FHIR resource at "http://fhirserver/Condition/?patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "subject" in all bundle resources references resource with ID "${data.patient-read-id}"

When Get FHIR resource at "http://fhirserver/Condition/?encounter=${data.encounter-read-in-progress-id}" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "encounter" in all bundle resources references resource with ID "${data.encounter-read-in-progress-id}"

When Get FHIR resource at "http://fhirserver/Condition/?recorded-date=ge2021-02-12" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(recordedDate }= @2021-02-12T00:00:00+01:00)' with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?recorded-date=le2050-01-01" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(recordedDate {= @2050-01-01T23:59:59+01:00)' with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?clinical-status=http://terminology.hl7.org/CodeSystem/condition-clinical%7Cactive" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(clinicalStatus.coding.code.where($this = 'active').exists())" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?_id=${data.condition-read-active-id}&clinical-status=http://terminology.hl7.org/CodeSystem/condition-clinical%7Cinactive" with content type "json"

And bundle does not contain resource "Condition" with ID "${data.condition-read-active-id}" with error message "The requested CodeSystem ${data.condition-read-active-id}} should not be part of the search result"

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(clinicalStatus.coding.code.where($this = "active").exists().not())' with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?clinical-status:not=http://terminology.hl7.org/CodeSystem/condition-clinical%7Cinactive" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(clinicalStatus.coding.code.where($this = "inactive").exists().not())' with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Condition/?category=encounter-diagnosis" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(category.coding.where(code = "encounter-diagnosis").exists())' with error message 'There are search results, but they do not fully match the search criteria'

Feature Coverage By Scenario

Test Outcomes

Test Performance

Key Statistics

Number of Scenarios 10 Total Duration 9s
Total Number of Test Cases 16 Fastest Test 216ms
Number of Manual Test Cases 0 Slowest Test 1s
Tests Started März 23, 2026 09:41:06 Average Execution Time 609ms
Tests Finished März 23, 2026 09:41:16 Total Execution Time 9s

Automated Tests

feature Scenario Context Steps Started Total Duration Result
Testing search parameters against a resource of type Condition (@Condition-Search) Precondition 2 09:41:06 430ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Read and Validation of the CapabilityStatement 2 09:41:07 696ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Validation of the search parameter definitions in the CapabilityStatement
7 passing test cases
1 09:41:07 1s 595ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by ID 3 09:41:09 968ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Tag 3 UNDEFINED
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Count 2 09:41:10 760ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Patient (Search Parameter 'subject') 3 09:41:11 1s 288ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Patient(Search Parameter 'patient') 3 09:41:12 907ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Encounter 3 09:41:13 972ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Recorded Date with 'ge' Modifier 3 09:41:14 1s 016ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Recorded Date with 'le' Modifier 3 09:41:15 1s 176ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Clinical Status 3 UNDEFINED
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by ID and Clinical Status 3 UNDEFINED
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Clinical Status with ':not' Modifier 3 UNDEFINED
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Category 3 UNDEFINED

Manual Tests

No manual tests were recorded
Serenity BDD version 4.3.2