Specifying Tests with DECOR - Revision history

Mligtvoet at 10:28, 3 December 2018

2018-12-03T10:28:32Z

2015-07-27T17:58:08Z

‎Generating HTML documentation

2015-02-06T21:41:41Z

‎concept = {@ref, @occurrence?, @predicate?, @assert}: typo

2015-02-04T20:16:41Z

‎Generating HTML documentation

2015-02-02T20:51:24Z

‎Generating HTML documentation

2014-07-23T07:01:15Z

‎concept = {@ref, @multiplicity, @predicate?}

2014-07-22T13:34:20Z

‎concept = {@ref, @occurrence, @assert}

2014-07-22T12:57:44Z

‎concept = {@ref, @multiplicity}

2014-06-03T07:54:51Z

‎suppliedConcepts

2014-06-03T07:52:53Z

‎testset

← Older revision		Revision as of 10:28, 3 December 2018
Line 147:		Line 147:
	describe in concept text what is wanted (the tester should enter 'Fentanyl' in		describe in concept text what is wanted (the tester should enter 'Fentanyl' in
	UI of the tested application), and state in @assert what code is required in the (HL7) message.		UI of the tested application), and state in @assert what code is required in the (HL7) message.
		+
		+	==More information on testing in ART-DECOR==
		+	For more information on testing in ART-DECOR, see [[XIS_maintenance]].

@@ Line 141: / Line 141: @@
 <syntaxhighlight lang="xml">
-<concept occurrence="2" assert="@code='N01AH01'" ref="2.16.840.1.113883.2.4.3.36.77.2.2.140090">Medication [2] must be "Fentanyl".</concept>
+<concept occurrence="2" assert="@code='N01AH01'"
 </syntaxhighlight>
 describe in concept text what is wanted (the tester should enter 'Fentanyl' in
 UI of the tested application), and state in @assert what code is required in the (HL7) message.

@@ Line 73: / Line 73: @@
 </syntaxhighlight>
-The counting of occurrences is document-wide at the moment. The test may contain a predicate, as with the multiplicities test. A concept test with an @assert should contain at least one of @occurrence or @predicate, and my contain both.
+The counting of occurrences is document-wide at the moment. The test may contain a predicate, as with the multiplicities test. A concept test with an @assert should contain at least one of @occurrence or @predicate, and may contain both.
 ===assert===

@@ Line 138: / Line 138: @@
 The XQuery in apps/xis/modules/get-test-description.xquery can be used to generate HTML documentation of the tests. Again, edit the XQuery to point to your {my-project}-tests.xml, and run it to generate a HTML page which describes all test requirements. This will contain all the texts inside testset/test/suppliedConcepts/concept.
-Best practive is to have the text inside the test/concept contain a functional description of the requirement, and have @assert contain the technical description. I.e.
+Best practice is to have the text inside the test/concept contain a functional description of the requirement, and have @assert contain the technical description. I.e.
 <syntaxhighlight lang="xml">

@@ Line 136: / Line 136: @@
 ==Generating HTML documentation==
-The XQuery in apps/xis/modules/get-test-description.xquery can be used to generate HTML documentation of the tests. Again, edit the XQuery to point to your {my-project}-tests.xml, and run it to generate a HTML page which describes all test requirements. This will contan all the texts inside testset/test/suppliedConcepts/concept.
+The XQuery in apps/xis/modules/get-test-description.xquery can be used to generate HTML documentation of the tests. Again, edit the XQuery to point to your {my-project}-tests.xml, and run it to generate a HTML page which describes all test requirements. This will contain all the texts inside testset/test/suppliedConcepts/concept.
 Best practive is to have the text inside the test/concept contain a functional description of the requirement, and have @assert contain the technical description. I.e.

@@ Line 51: / Line 51: @@
 If a predicate attribute is added (i.e. predicate="../hl7:code[@code='445872007']") then this predicate is applied to the node set before the occurrences are counted. In this case, only occurrences which have a parent with a code 445872007 are counted. For predicates:
-* use single quotes only
+* use single quotes only,
-* do not include square brackets.
+* do not include the outer square brackets, they will be supplied when the schematron is generated.
 ====concept = {@ref, @occurrence?, @predicate?, @assert}====

@@ Line 39: / Line 39: @@
 concepts occur in two forms:
-====concept = {@ref, @multiplicity}====
+====concept = {@ref, @multiplicity, @predicate?}====
 This form will require the concept which @ref points to, to occur in the tested message the number of times @multiplicity states.
@@ Line 49: / Line 49: @@
 This would require the concept with @id '2.16.840.1.113883.2.4.3.36.77.2.2.125059' to occur twice in a tested message. The text in the concept clause is shown if the condition is not met.
 ====concept = {@ref, @occurrence, @assert}====

@@ Line 34: / Line 34: @@
 ===suppliedConcepts===
-suppliedConcepts = {concept+}
+suppliedConcepts = {concept*, assert*}
 ===concept===
 concepts occur in two forms:

@@ Line 14: / Line 14: @@
 The content model of testset = {@name, @version?, release, test+}.
 * @name: a name for the testset
-* @version: the release of DECOR. It is for documentation purposes only
+* @version: the release of DECOR, it is for documentation purposes only (the DECOR information is retrieved through release/@uri)
 ===release===