Surefire Report

Summary

[Summary] [Package List] [Test Cases]


Tests Errors Failures Skipped Success Rate Time
148 8 10 0 87.838% 0.215

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
78 6 4 0 87.179% 0.127
| openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 | Adverse reaction list | openEHR-EHR-EVALUATION.adverse_reaction_risk 11 0 0 0 100% 0.036
| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test 12 0 2 0 83.333% 0.008
| openEHR-EHR-COMPOSITION.medication_list 11 2 0 0 81.818% 0.014
| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration 12 0 2 0 83.333% 0.01
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order 24 0 2 0 91.667% 0.02

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.031
Scenario: Query openEHR data using session based EHR Id 7 0 0 0 100% 0.02
Scenario: Commit composition in flat json format 7 0 0 0 100% 0.021
Scenario: Commit composition in flat json and retrieve raw format 8 0 2 0 75% 0.014
Scenario: Commit composition in flat json and retrieve xml format 8 0 0 0 100% 0.013
Scenario: Select data item using its archetype node id and name 9 0 2 0 77.778% 0.003
Scenario: Select instruction under section 8 2 0 0 75% 0.005
Scenario: Select evaluation under section 8 0 0 0 100% 0.015
Scenario: Select observation under section 8 2 0 0 75% 0.001
Scenario: Select action under section 8 2 0 0 75% 0.004

| openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 | Adverse reaction list | openEHR-EHR-EVALUATION.adverse_reaction_risk

Class Tests Errors Failures Skipped Success Rate Time
v1 | 11 0 0 0 100% 0.036

| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test

Class Tests Errors Failures Skipped Success Rate Time
v1 | 12 0 2 0 83.333% 0.008

| openEHR-EHR-COMPOSITION.medication_list

Class Tests Errors Failures Skipped Success Rate Time
v0 | Medication statement list | 11 2 0 0 81.818% 0.014

| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration

Class Tests Errors Failures Skipped Success Rate Time
v1 | 12 0 2 0 83.333% 0.01

| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order

Class Tests Errors Failures Skipped Success Rate Time
v1 | 24 0 2 0 91.667% 0.02

Test Cases

[Summary] [Package List] [Test Cases]

Scenario: Query openEHR data using AQL over REST

Given The server is running 0.004
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.001
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.026

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
Scenario: Query openEHR data using session based EHR Id 0.02

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
Then A composition id should be returned by the API 0.001
Scenario: Commit composition in flat json format 0.02

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
Then A composition id should be returned by the API 0
And Composition id should allow retrieval of composition in raw format
+ [ Detail ]
 0.007
Scenario: Commit composition in flat json and retrieve raw format
+ [ Detail ]
 0.007

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.001
Scenario: Commit composition in flat json and retrieve xml format 0.012

v1 |

Given The server is running 0
Given The server is running 0
And The client system is logged into a server session 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 The templates with following ids are available to the server: 0
And An EHR is created 0.001
And An EHR is created 0
And The following compositions exists under the EHR: 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 The query contains EHR id criteria 0
And Composition archetype id is openEHR-EHR-COMPOSITION.medication_list.v0 0
And Composition archetype id is openEHR-EHR-COMPOSITION.medication_list.v0 0
And Composition name criteria using WHERE clause is Medication statement list 0.001
And Composition name criteria using WHERE clause is Medication statement list 0.001
And Instruction archetype id is openEHR-EHR-INSTRUCTION.medication_order.v1 0
And Instruction archetype id is openEHR-EHR-INSTRUCTION.medication_order.v1 0
Then The following data items should be available in query results: 0
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order.v1 | 0.015
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order.v1 |
+ [ Detail ]
 0.001
expected:<openEHR-EHR-INSTRUCTION.medication_order.v1> but was:<null>
When A an AQL query that describes an instruction under an EHR is created 0
Then The results should be instruction instances
+ [ Detail ]
 0
expected:<openEHR-EHR-INSTRUCTION.medication_order.v1> but was:<null>

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
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 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.002
Values should be different. Actual: 2 puffs

v0 | Medication statement list |

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.008
When A an AQL query that describes a composition under an EHR is created 0.003
And The query contains EHR id criteria 0
And Composition archetype id is openEHR-EHR-COMPOSITION.medication_list.v0 0
And Composition name criteria using WHERE clause is Medication statement list 0
Then The results should be composition instances
+ [ Detail ]
 0.001
Failed to parse the JSON document
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list |
+ [ Detail ]
 0.002
Failed to parse the JSON document

v1 |

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.001
And The following compositions exists under the EHR: 0
When A an AQL query that describes an instruction under an EHR is created 0
And The query contains EHR id criteria 0.001
And Composition archetype id is openEHR-EHR-COMPOSITION.request.v1 0.001
And Composition name criteria using WHERE clause is Laboratory order 0
And Instruction archetype id is openEHR-EHR-INSTRUCTION.request-lab_test.v1 0
Then The results should be instruction instances
+ [ Detail ]
 0.002
expected:<openEHR-EHR-INSTRUCTION.request-lab_test.v1> but was:<null>
| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test.v1 |
+ [ Detail ]
 0.003
expected:<openEHR-EHR-INSTRUCTION.request-lab_test.v1> but was:<null>

v1 |

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
When A an AQL query that describes an evalution under an EHR is created 0
And The Composition archetype id is openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 0
And Composition name criteria using WHERE clause is Adverse reaction list 0
And Evaluation archetype id is openEHR-EHR-EVALUATION.adverse_reaction_risk.v1 0
Then The results should be evaluation instances 0.009
| openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 | Adverse reaction list | openEHR-EHR-EVALUATION.adverse_reaction_risk.v1 | 0.026

v1 |

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.003
And An EHR is created 0
And The following compositions exists under the EHR: 0
When A an AQL query that describes an observation under an EHR is created 0
And The query contains EHR id criteria 0
And The Composition archetype id is openEHR-EHR-COMPOSITION.encounter.v1 0
And Composition name criteria using WHERE clause is Vital Signs Observations 0
And Observation archetype id is openEHR-EHR-OBSERVATION.respiration.v1 0
Then The results should be observation instances
+ [ Detail ]
 0.003
expected:<openEHR-EHR-OBSERVATION.respiration.v1> but was:<null>
| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration.v1 |
+ [ Detail ]
 0.004
expected:<openEHR-EHR-OBSERVATION.respiration.v1> but was:<null>

Scenario: Select instruction under section

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 section is created 0.004
Then The results should include instruction instances
+ [ Detail ]
 0
Scenario: Select instruction under section
+ [ Detail ]
 0.001

Scenario: Select evaluation under section

Given The server is running 0.001
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 evalution under a section is created 0
Then The results should include evaluation instances 0
Scenario: Select evaluation under section 0.014

Scenario: Select observation under section

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 observation under a section is created 0
Then The results should include observation instances
+ [ Detail ]
 0
Scenario: Select observation under section
+ [ Detail ]
 0.001

Scenario: Select action under section

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.001
And The following compositions exists under the EHR: 0
When A an AQL query that describes an action under a section is created 0
Then The results should include action instances
+ [ Detail ]
 0.001
Failed to parse the JSON document
Scenario: Select action under section
+ [ Detail ]
 0.002
Failed to parse the JSON document

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:
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order.v1 |
java.lang.AssertionError: expected:<openEHR-EHR-INSTRUCTION.medication_order.v1> but was:<null>
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order.v1 |:
Then The results should be instruction instances
java.lang.AssertionError: expected:<openEHR-EHR-INSTRUCTION.medication_order.v1> but was:<null>
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list | openEHR-EHR-INSTRUCTION.medication_order.v1 |:
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:
Then The results should be composition instances
com.jayway.restassured.path.json.exception.JsonPathException: Failed to parse the JSON document
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list |:
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list |
com.jayway.restassured.path.json.exception.JsonPathException: Failed to parse the JSON document
| openEHR-EHR-COMPOSITION.medication_list.v0 | Medication statement list |:
Then The results should be instruction instances
java.lang.AssertionError: expected:<openEHR-EHR-INSTRUCTION.request-lab_test.v1> but was:<null>
| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test.v1 |:
| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test.v1 |
java.lang.AssertionError: expected:<openEHR-EHR-INSTRUCTION.request-lab_test.v1> but was:<null>
| openEHR-EHR-COMPOSITION.request.v1 | Laboratory order | openEHR-EHR-INSTRUCTION.request-lab_test.v1 |:
Then The results should be observation instances
java.lang.AssertionError: expected:<openEHR-EHR-OBSERVATION.respiration.v1> but was:<null>
| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration.v1 |:
| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration.v1 |
java.lang.AssertionError: expected:<openEHR-EHR-OBSERVATION.respiration.v1> but was:<null>
| openEHR-EHR-COMPOSITION.encounter.v1 | Vital Signs Observations | openEHR-EHR-OBSERVATION.respiration.v1 |:
Then The results should include instruction instances
java.lang.NullPointerException
Scenario: Select instruction under section:
Scenario: Select instruction under section
java.lang.NullPointerException
Scenario: Select instruction under section:
Then The results should include observation instances
java.lang.NullPointerException
Scenario: Select observation under section:
Scenario: Select observation under section
java.lang.NullPointerException
Scenario: Select observation under section:
Then The results should include action instances
com.jayway.restassured.path.json.exception.JsonPathException: Failed to parse the JSON document
Scenario: Select action under section:
Scenario: Select action under section
com.jayway.restassured.path.json.exception.JsonPathException: Failed to parse the JSON document
Scenario: Select action under section: