Serenity BDD Report
Home > Tag > Precondition
Report generated 23-03-2026 09:42:04

Tag: Precondition

40 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 40
Total Number of Test Cases 40
Tests Started März 23, 2026 09:36:16
Tests Finished März 23, 2026 09:41:46
Total Duration 5m 29s
Fastest Test 412ms
Slowest Test 1s
Average Execution Time 442ms
Total Execution Time 17s

Functional Coverage Details

Features

Feature Scenarios Test Cases % Pass Result Coverage
Stufe5 > basis > Read Information from a resource of type Account (@Account-Read) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type Account (@Account-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Binary (@Binary-Read) 1 1 100%
Stufe5 > basis > Upload of a Document Bundle with POST Operation (@Composition-Post) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type Condition (@Condition-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) 1 1 100%
Stufe5 > basis > Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Patient (@Patient-Read) 1 1 100%
Stufe5 > basis > Read extended Information from a resource of type Patient (@Patient-Read-Extended) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type Patient (@Patient-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Practitioner (@Practitioner-Read) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type Procedure (@Procedure-Read) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type Procedure (@Procedure-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 1 1 100%
Stufe5 > basis > Read Information from a resource of type ValueSet (@ValueSet-Read) 1 1 100%
Stufe5 > basis > Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 1 1 100%
Stufe5 > dokumentenaustausch > Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 1 1 100%
Stufe5 > dokumentenaustausch > Read information from a resource of type DocumentReference (@DocumentReference-Read) 1 1 100%
Stufe5 > dokumentenaustausch > Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 1 1 100%
Stufe5 > terminplanung > Booking an appointment (@Appointment-Book) 1 1 100%
Stufe5 > terminplanung > Booking an appointment by schedule reference (@Appointment-Book-By-Schedule) 1 1 100%
Stufe5 > terminplanung > Read Information from a resource of type Appointment (@Appointment-Read) 1 1 100%
Stufe5 > terminplanung > Testing search parameters against the Appointment resource (@Appointment-Search) 1 1 100%
Stufe5 > terminplanung > Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) 1 1 100%
Stufe5 > terminplanung > Read Information from a resource of type HealthcareService (@HealthcareService-Read) 1 1 100%
Stufe5 > terminplanung > Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 1 1 100%
Stufe5 > terminplanung > Read Information from a resource of type Schedule (@Schedule-Read) 1 1 100%
Stufe5 > terminplanung > Testing search parameters against the Schedule resource (@Schedule-Search) 1 1 100%
Stufe5 > terminplanung > Read Information from a resource of type Slot (@Slot-Read) 1 1 100%
Stufe5 > terminplanung > Testing search parameters against the Slot resource (@Slot-Search) 1 1 100%

Key Statistics

Number of Scenarios 40 Total Duration 5m 29s
Total Number of Test Cases 40 Fastest Test 412ms
Number of Manual Test Cases 0 Slowest Test 1s
Tests Started März 23, 2026 09:36:16 Average Execution Time 442ms
Tests Finished März 23, 2026 09:41:46 Total Execution Time 17s

Automated Scenarios

feature Scenario Context Steps Started Total Duration Result
Read Information from a resource of type Account (@Account-Read) Precondition 2 09:37:49 414ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Precondition 2 09:41:16 428ms SUCCESS
Read Information from a resource of type Binary (@Binary-Read) Precondition 2 09:41:03 430ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) Precondition 2 09:37:42 422ms SUCCESS
Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) Precondition 2 09:38:30 423ms SUCCESS
Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) Precondition 2 09:41:26 431ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Precondition 2 09:41:06 430ms SUCCESS
Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) Precondition 2 09:39:14 418ms SUCCESS
Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) Precondition 2 09:40:08 429ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Precondition 2 09:36:16 1s 232ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Precondition 2 09:37:16 422ms SUCCESS
Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) Precondition 2 09:37:10 417ms SUCCESS
Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) Precondition 2 09:37:05 412ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Precondition 2 09:37:37 417ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Precondition 2 09:38:36 425ms SUCCESS
Read Information from a resource of type Patient (@Patient-Read) Precondition 2 09:41:32 433ms SUCCESS
Read extended Information from a resource of type Patient (@Patient-Read-Extended) Precondition 2 09:39:35 423ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Precondition 2 09:40:25 435ms SUCCESS
Read Information from a resource of type Practitioner (@Practitioner-Read) Precondition 2 09:38:13 422ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Precondition 2 09:37:24 416ms SUCCESS
Read Information from a resource of type Procedure (@Procedure-Read) Precondition 2 09:36:31 415ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Precondition 2 09:39:54 426ms SUCCESS
Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) Precondition 2 09:39:04 428ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Precondition 2 09:39:21 417ms SUCCESS
Read Information from a resource of type ValueSet (@ValueSet-Read) Precondition 2 09:39:39 421ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Precondition 2 09:41:36 424ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) Precondition 2 09:40:12 431ms SUCCESS
Read information from a resource of type DocumentReference (@DocumentReference-Read) Precondition 2 09:37:56 421ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Precondition 2 09:38:17 417ms SUCCESS
Booking an appointment (@Appointment-Book) Precondition 2 09:39:49 425ms SUCCESS
Booking an appointment by schedule reference (@Appointment-Book-By-Schedule) Precondition 2 09:36:27 416ms SUCCESS
Read Information from a resource of type Appointment (@Appointment-Read) Precondition 2 09:39:08 422ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Precondition 2 09:41:45 428ms SUCCESS
Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) Precondition 2 09:40:58 429ms SUCCESS
Read Information from a resource of type HealthcareService (@HealthcareService-Read) Precondition 2 09:39:17 419ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Precondition 2 09:39:27 427ms SUCCESS
Read Information from a resource of type Schedule (@Schedule-Read) Precondition 2 09:37:34 419ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Precondition 2 09:36:56 417ms SUCCESS
Read Information from a resource of type Slot (@Slot-Read) Precondition 2 09:37:53 413ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Precondition 2 09:38:05 420ms SUCCESS

Manual Tests

No manual tests were recorded
Serenity BDD version 4.3.2