Surefire Report

Summary

[Summary] [Package List] [Test Cases]


Tests Errors Failures Skipped Success Rate Time
92 6 4 8 80.435% 0.16

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
81 6 4 8 77.778% 0.142
| openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 | Adverse reaction list | openEHR-EHR-EVALUATION.adverse_reaction_risk 11 0 0 0 100% 0.018

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.025
Scenario: Query openEHR data using session based EHR Id 7 0 0 0 100% 0.014
Scenario: Commit composition in flat json format 7 0 0 0 100% 0.008
Scenario: Commit composition in flat json and retrieve raw format 8 0 2 0 75% 0.04
Scenario: Commit composition in flat json and retrieve xml format 8 0 0 0 100% 0.021
Scenario: Select composition and instruction data when Composition contains instruction 12 2 0 3 58.333% 0.007
Scenario: Select data item using its archetype node id and name 9 0 2 0 77.778% 0.017
Scenario: Select composition 11 2 0 2 63.636% 0.007
Scenario: Select instruction 12 2 0 3 58.333% 0.003

| 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.018

Test Cases

[Summary] [Package List] [Test Cases]

Scenario: Query openEHR data using AQL over REST

Given The server is running 0.003
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.022

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.001
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.013

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
Scenario: Commit composition in flat json format 0.008

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

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.02

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.001
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
+ [ Detail ]
 0.002
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition and instruction data when Composition contains instruction
+ [ Detail ]
 0.003
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
And Composition name criteria using WHERE clause
+ [ Detail ]
 0
skipped
And Instruction archetype id criteria
+ [ Detail ]
 0
skipped
Then The following data items should be available in query results:
+ [ Detail ]
 0
skipped

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.002
And The following compositions exists under the EHR: 0.007
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.005
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

Scenario: Select composition

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 a composition under an EHR is created 0
And The query contains EHR id criteria 0
And Composition archetype id criteria
+ [ Detail ]
 0.003
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition
+ [ Detail ]
 0.004
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
And Composition name criteria using WHERE clause
+ [ Detail ]
 0
skipped
Then The results should be composition instances
+ [ Detail ]
 0
skipped

Scenario: Select 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 an EHR is created 0
And The query contains EHR id criteria 0
And Composition archetype id criteria
+ [ Detail ]
 0.001
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select instruction
+ [ Detail ]
 0.002
Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
And Composition name criteria using WHERE clause
+ [ Detail ]
 0
skipped
And Instruction archetype id criteria
+ [ Detail ]
 0
skipped
Then The results should be instruction instances
+ [ Detail ]
 0
skipped

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
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
| openEHR-EHR-COMPOSITION.adverse_reaction_list.v1 | Adverse reaction list | openEHR-EHR-EVALUATION.adverse_reaction_risk.v1 | 0.018

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:
And Composition archetype id criteria
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition and instruction data when Composition contains instruction:
Scenario: Select composition and instruction data when Composition contains instruction
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition and instruction data when Composition contains instruction:
And Composition name criteria using WHERE clause
skipped: skipped
And Instruction archetype id criteria
skipped: skipped
Then The following data items should be available in query results:
skipped: skipped
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:
And Composition archetype id criteria
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition:
Scenario: Select composition
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select composition:
And Composition name criteria using WHERE clause
skipped: skipped
Then The results should be composition instances
skipped: skipped
And Composition archetype id criteria
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select instruction:
Scenario: Select instruction
cucumber.runtime.CucumberException: Arity mismatch: Step Definition 'com.ethercis.vehr.AqlFeaturesSteps.compositionArchetypeIdCriteria(String) in file:/home/travis/build/serefarikan/VirtualEhr/vehr-integration-tests/target/test-classes/' with pattern [^Composition archetype id criteria$] is declared with 1 parameters. However, the gherkin step has 0 arguments []. Step: And Composition archetype id criteria
Scenario: Select instruction:
And Composition name criteria using WHERE clause
skipped: skipped
And Instruction archetype id criteria
skipped: skipped
Then The results should be instruction instances
skipped: skipped