Setting scenario.resolveProperties=false to true will break this test.

Why?

Because in your input-file for one of the steps there is:

${extraElementen:kvkNummer} which is meant to be resolved by the Json2Xml pipe (or perhaps another pipe, I didn't check the pipeline yet) however it is now resolved by Larva.

Larva has this feature to put things like the host & port in input files, which it needs for some tests (from top of my head, I think API Listener Larva tests need that).

Setting scenario.resolveProperties=false to true will break this test.
Why?

Because in your input-file for one of the steps there is:

${extraElementen:kvkNummer} which is meant to be resolved by the Json2Xml pipe (or perhaps another pipe, I didn't check the pipeline yet) however it is now resolved by Larva.

Larva has this feature to put things like the host & port in input files, which it needs for some tests (from top of my head, I think API Listener Larva tests need that).

In Zaakbrug we have translation profiles(configurable by user via a json file) for configuring custom mappings. With ${extraElementen:kvkNummer} you tell ZaakBrug to dynamically replace a certain element's value with the value of extraElementen element where name="kvkNummer" from the input message. It happens to use the same syntax as used for properties, but it has absolutely nothing to do with it. There are XSLT's for handling this syntax.

Setting scenario.resolveProperties=false to true will break this test.
Why?

Because in your input-file for one of the steps there is:
${extraElementen:kvkNummer} which is meant to be resolved by the Json2Xml pipe (or perhaps another pipe, I didn't check the pipeline yet) however it is now resolved by Larva.
Larva has this feature to put things like the host & port in input files, which it needs for some tests (from top of my head, I think API Listener Larva tests need that).

In Zaakbrug we have translation profiles(configurable by user via a json file) for configuring custom mappings. With ${extraElementen:kvkNummer} you tell ZaakBrug to dynamically replace a certain element's value with the value of extraElementen element where name="kvkNummer" from the input message. It happens to use the same syntax as used for properties, but it has absolutely nothing to do with it. There are XSLT's for handling this syntax.

Yes, so unfortunately a change that was made in 9.2 or 9.3 (don't remember on top of my head which version) broke this out-of-the-box for your use-cases and this Larva setting needs to be changed in the scenarios.

We could consider making a global default so that this can be toggled for all scenarios at once.

If you have a common properties file shared between all tests, you can set this property

scenario.resolveProperties=false

once in this shared properties file to disable it for all your Larva tests.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud