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

Feature: Testing search parameters against a resource of type "statutory" coverage (@coverage-search-statutory)

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 Coverage-Read-Statutory 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 "Coverage"

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

Examples:

searchParamValuesearchParamType
_idtoken
_countnumber
statustoken
typetoken
beneficiaryreference
payorreference

Examples:

searchParamValuesearchParamType
_tagtoken 
subscriberreference 

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

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

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

When Get FHIR resource at "http://fhirserver/Coverage/?patient.identifier=http://fhir.de/sid/gkv/kvid-10%7CX485231029" 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 response bundle contains resource with ID "${data.coverage-read-statutory-id}" with error message "The requested Coverage ${data.coverage-read-statutory-id} is not contained in the response bundle"

When Get FHIR resource at "http://fhirserver/Coverage/?status=active" 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(status='active')" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Coverage/?type=GKV" 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(type.coding.code='GKV')" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Coverage/?beneficiary=${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 "beneficiary" in all bundle resources references resource with ID "${data.patient-read-id}"

When Get FHIR resource at "http://fhirserver/Coverage/?type=SEL" with content type "json"

And bundle does not contain resource "Coverage" with ID "${data.coverage-read-statutory-id}" with error message "There are search results, but they do not fully match the search criteria"

And FHIR current response body evaluates the FHIRPath "entry.resource.ofType(Coverage).all(type.coding.code='SEL')" 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 9 Total Duration 8s
Total Number of Test Cases 14 Fastest Test 210ms
Number of Manual Test Cases 0 Slowest Test 1s
Tests Started März 23, 2026 09:37:16 Average Execution Time 601ms
Tests Finished März 23, 2026 09:37:24 Total Execution Time 8s

Automated Tests

feature Scenario Context Steps Started Total Duration Result
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Precondition 2 09:37:16 422ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Read and Validation of the CapabilityStatement 2 09:37:16 817ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:37:17 1s 306ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by ID 3 09:37:18 943ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by insured person's number 3 09:37:19 940ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Status 3 09:37:20 1s 065ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Type 3 09:37:21 895ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Beneficiary 3 09:37:22 1s 019ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Type (Negative Test) 3 09:37:23 1s 050ms SUCCESS

Manual Tests

No manual tests were recorded
Serenity BDD version 4.3.2