Surefire Report

Summary

[Summary] [Package List] [Test Cases]


Tests Errors Failures Skipped Success Rate Time
58 0 4 0 93.103% 0.123

Note: failures are anticipated and checked for with assertions while errors are unanticipated.


Package List

[Summary] [Package List] [Test Cases]


Package Tests Errors Failures Skipped Success Rate Time
58 0 4 0 93.103% 0.123

Note: package statistics are not computed recursively, they only sum up all of its testsuites numbers.

Class Tests Errors Failures Skipped Success Rate Time
Scenario: Query openEHR data using AQL over REST 7 0 0 0 100% 0.033
Scenario: Query openEHR data using session based EHR Id 7 0 0 0 100% 0.022
Scenario: Commit composition in flat json format 7 0 0 0 100% 0.013
Scenario: Commit composition in flat json and retrieve raw format 8 0 2 0 75% 0.023
Scenario: Commit composition in flat json and retrieve xml format 8 0 0 0 100% 0.009
Scenario: Select composition and instruction data when Composition contains instruction 12 0 0 0 100% 0.014
Scenario: Select data item using its archetype node id and name 9 0 2 0 77.778% 0.009

Test Cases

[Summary] [Package List] [Test Cases]

Scenario: Query openEHR data using AQL over REST

Given The server is running 0.002
And The client system is logged into a server session 0
And The openEHR template prescription.opt for the composition is available to the server 0
And An EHR is created 0
When A composition is persisted under the EHR 0
Then An AQL query should return data from the composition in the EHR 0
Scenario: Query openEHR data using AQL over REST 0.031

Scenario: Query openEHR data using session based EHR Id

Given The server is running 0
And The client system is logged into a server session 0
And The openEHR template prescription.opt for the composition is available to the server 0
And An EHR is created 0
When A composition is persisted under the EHR without an EHR identifier 0
Then An AQL query should return data from the composition in the EHR 0.005
Scenario: Query openEHR data using session based EHR Id 0.017

Scenario: Commit composition in flat json format

Given The server is running 0
And The client system is logged into a server session 0
And The openEHR template IDCR - Immunisation summary.v0.opt for the composition is available to the server 0
And An EHR is created 0
When Flat json file IDCR - Immunisation summary.v0.flat.json with template id IDCR - Immunisation summary.v0 is committed to service 0.001
Then A composition id should be returned by the API 0
Scenario: Commit composition in flat json format 0.012

Scenario: Commit composition in flat json and retrieve raw format

Given The server is running 0
And The client system is logged into a server session 0
And The openEHR template IDCR - Immunisation summary.v0.opt for the composition is available to the server 0
And An EHR is created 0
When Flat json file IDCR - Immunisation summary.v0.flat.json with template id IDCR - Immunisation summary.v0 is committed to service 0.006
Then A composition id should be returned by the API 0
And Composition id should allow retrieval of composition in raw format
+ [ Detail ]
 0.008
Scenario: Commit composition in flat json and retrieve raw format
+ [ Detail ]
 0.009

Scenario: Commit composition in flat json and retrieve xml format

Given The server is running 0
And The client system is logged into a server session 0
And The openEHR template IDCR - Immunisation summary.v0.opt for the composition is available to the server 0
And An EHR is created 0
When Flat json file IDCR - Immunisation summary.v0.flat.json with template id IDCR - Immunisation summary.v0 is committed to service 0
Then A composition id should be returned by the API 0
And Composition id should allow retrieval of composition in xml format 0
Scenario: Commit composition in flat json and retrieve xml format 0.009

Scenario: Select composition and instruction data when Composition contains instruction

Given The server is running 0
And The client system is logged into a server session 0
And The templates with following ids are available to the server: 0
And An EHR is created 0
And The following compositions exists under the EHR: 0
When A an AQL query that describes an instruction under a composition is created 0.001
And The query contains EHR id criteria 0
And Composition archetype id criteria 0
And Composition name criteria using WHERE clause 0
And Instruction archetype id criteria 0.001
Then The following data items should be available in query results: 0
Scenario: Select composition and instruction data when Composition contains instruction 0.012

Scenario: Select data item using its archetype node id and name

Given The server is running 0
And The client system is logged into a server session 0.001
And The templates with following ids are available to the server: 0
And An EHR is created 0
And The following compositions exists under the EHR: 0.001
When An AQL query that selects composition uids and data items is created 0
And The data items are selected based on both archetype node id and name 0
Then Data items with same node id should have different values if they have different names
+ [ Detail ]
 0.001
Values should be different. Actual: 2 puffs
Scenario: Select data item using its archetype node id and name
+ [ Detail ]
 0.006
Values should be different. Actual: 2 puffs

Failure Details

[Summary] [Package List] [Test Cases]


And Composition id should allow retrieval of composition in raw format
java.lang.AssertionError
Scenario: Commit composition in flat json and retrieve raw format:
Scenario: Commit composition in flat json and retrieve raw format
java.lang.AssertionError
Scenario: Commit composition in flat json and retrieve raw format:
Then Data items with same node id should have different values if they have different names
java.lang.AssertionError: Values should be different. Actual: 2 puffs
Scenario: Select data item using its archetype node id and name:
Scenario: Select data item using its archetype node id and name
java.lang.AssertionError: Values should be different. Actual: 2 puffs
Scenario: Select data item using its archetype node id and name: