-
Notifications
You must be signed in to change notification settings - Fork 5
ELZ 0.2.0-beta test material #161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@jduwel kan jij mijn PR reviewen? Dit is Testmateriaal voor de beta publicatie van Eerstelijnszorg waarbij alleen het sturen/ontvangen van drie testscripts getest wordt. |
jd-nictiz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Door gebrek aan validatie-assert kan ik verder weinig zeggen over de inhoud van de fixtures. Ben benieuwd of je ze al ergens hebt gevalideerd.
src/ELZ-0-2-0-beta/Test/Receiving-XIS/elz-receiving-xis-scenario-1-maximal.xml
Outdated
Show resolved
Hide resolved
src/ELZ-0-2-0-beta/Test/Receiving-XIS/elz-receiving-xis-scenario-1-maximal.xml
Outdated
Show resolved
Hide resolved
src/ELZ-0-2-0-beta/Test/Receiving-XIS/elz-receiving-xis-scenario-1-maximal.xml
Outdated
Show resolved
Hide resolved
src/ELZ-0-2-0-beta/Test/Receiving-XIS/elz-receiving-xis-scenario-1-maximal.xml
Outdated
Show resolved
Hide resolved
src/ELZ-0-2-0-beta/Test/Serving-XIS/elz-serving-xis-scenario-1-maximal.xml
Outdated
Show resolved
Hide resolved
|
Wellicht ook een goed moment om vanaf het begin de 'content asserts' toe te voegen. Zie Alexander of Pieter voor meer informatie om te kijken of dat past |
Goeie, maar dit willen we op langer termijn gaan toevoegen zodra de release (uit beta) stabiel genoeg. |
|
Met dank aan Pieter zijn de zaken die Jorn eerder aangekaart zijn opgelost. Load https://touchstone.aegis.net/touchstone/execution?exec=202410091029309853529994 Aantal content asserts foutmeldingen naar voren gekomen dat mogelijk een bug is. Hiervoor een ticket aangemaakt: https://nictiz.atlassian.net/browse/HIT-35 |
|
Load: https://touchstone.aegis.net/touchstone/execution?exec=202411280444051942534023 Scripts: https://touchstone.aegis.net/touchstone/execution?exec=202411280458239189057128 @pieter-edelman-nictiz Kan jij mijn PR controleren voor ELZ? Dank! |
| value="Serve Task resource"/> | ||
| <nts:include value="test.server.successfulRead" scope="common" | ||
| resource="Task" | ||
| params="/task-hg-VerwijzingHuisartsParamedicusMaximaalbericht" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem correct. How do you expect a server to work with a fixed resource id? How would the client now what id to read?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<variable>
<name value="TaskID"/>
<description value="...."/>
</variable><nts:include value="test.server.successfulRead" scope="common"
resource="Task"
params="/{TaskID}"| <name value="Scenario 1.2 - ServiceRequest"/> | ||
| <description value="Serve ServiceRequest resource"/> | ||
| <nts:include value="test.server.successfulRead" scope="common" resource="ServiceRequest" | ||
| params="/servicerequest-hg-VerwijzingHuisartsParamedicusMaximaalbericht" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the test platform extract the resource reference from the Task?
| <name value="Scenario 1.3 - Composition"/> | ||
| <description value="Serve Composition resource with all the references by using the Document operation"/> | ||
| <nts:include value="test.server.successfulRead" scope="common" resource="Composition" | ||
| params="/composition-hg-VerwijzingHuisartsParamedicusMaximaalbericht" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the test platform extract the resource reference from the Task?
| <nts:contentAsserts href="resources/task-hg-VerwijzingHuisartsParamedicusMaximaalbericht.xml" | ||
| description="contains .code.coding.code = '3457005'" discriminator="code.where(coding.where(code = '3457005'))" nts:in-targets="CheckContent"/> | ||
|
|
||
| </test> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These server scripts don't perform profile valdation. It would be a good idea to add that.
pieter-edelman-nictiz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ik snap eerlijk gezegd niet hoe dit zou moeten werken. De scripts beginnen er nu mee dat de Receiving XIS een read doet op de Task bij de Serving XIS, maar het .id is hardcoded in the TestScript.
In het TO staat dat er een notificatie-mechanisme moet zijn om die .id te communiceren, zobder dat mechanisme te specificeren. Zou dat tot nader order vervangen kunnen worden door een variabele in het TestScript dat je bij aanvang moet invoeren?
|
Jorn helped with the FHIR-path expression for the referenceID's, and now it's working. Load: https://my.interoplab.eu/uc-nictiz/tests/instance/68a46ad673acc15a1072943e @pieter-edelman-nictiz are you able to review this PR? |
pieter-edelman-nictiz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR is akkoord. De afspraak is dat materialen die nog niet in definitieve versie zijn ook niet gepubliceerd worden naar main.
|
I'll close this PR because of the beta status of the materials. When it is released (v1.0.0), it could be merged to main (production) |
No description provided.