StUF Testplatform : Corrections required in ZSDMS 1.2 compliance test scenarios

[surajpunugade]

I am Suraj Punugade, reporting the issues on behalf of Decos

Decos is working on ZSDMS 1.2 compliance. For that, we have set up test environment and executing ZsDMS 1.2 test scenarios from https://stuftestplatform.nl/. While executing the test cases, we came across a few scenarios which are not proper. Below are the proposed corrections in those test cases.

1. maakZaakDocumenten_edclk01 and voegZaakdocumentToe_edclk01 requests

Issue:
The requests don’t specify bestandname along with file extension or content-type attribute.
Below is one of the configured voegZaakdocumentToe_edclk01 request

Details:
Cross checked these requests for Zaak-en documentservices 1.0 test cases. It contains ‘bestandname’ with file extension and contentType attribute, as you can see in below screenshot –

Expected:
maakZaakDocumenten_edclk01 and voegZaakdocumentToe_edclk01 requests should contain bestandname along with file extension.
 

2. geefLijstZaakdocumenten_Lv01 and geefZaakdocumentLezen_EdcLv01 requests

Issue:
Zender and Ontavanger details are not specified in the configured requests.

Details:
Below is the screenshot of one of the configured geefLijstZaakdocumenten_Lv01 request

Expected:
geefLijstZaakdocumenten_Lv01 and geefZaakdocumentLezen_ EdcLv01 requests should contain Zender and Ontavanger nodes.

 

3. geefZaakdetails_ZakLv01 Test cases validation

Issue:
Expected geefZaakdetails_ZakLa01 response message contains fixed identificatie value.

Details:
Faced below validation error

The expected response has fixed values, refer below screenshot

Expected:
geefZaakdetails_ZakLv01 request is sent in the follwing sequence

• genereerZaakIdentificatie_Di02
• creeerZaak_Lk01
• updateZaak_Lk01
• geefZaakdetails_ZakLv01

It's expected that sub-case and relevant-case identificaties should be used from appropriate previous requests e.g. genereerZaakIdentificatie_Di02