Page History

...

accountManagement:
  registration:
    emailRegistrationEnabled: true
    phoneRegistrationEnabled: true

...

...
<configuration comment="Disabling registration via phone, enabling registration via email">
    <property path="accountManagement.registration.phoneRegistrationEnabled" value="false"/>
    <property path="accountManagement.registration.emailRegistrationEnabled" value="truefalse"/>
</configuration>
...

So, the next step in the scenario, the system will behave as the properties above have the value false. Such behavior will last until the end of the scenario or until properties' values will be changed again.

You can specify as many properties as you need. Also you can use the tag <configuration> itself as many times as you need.

...

If you don't need all properties to be included in GlobalConfigurationPathResolver, you can list only required the highest level properties to include. For this separate them with comma (no spaces, just comma!).

For example, if you has the following configuration file

...

cmd/run generate cfg-with-resolver --exclude geoLite2

NOTE: After test scenario completion all changed properties' values are reverted to their values before changing via tag <configuration> (values which were stated in configuration file).

If you have any questions/suggestions feel free to contact Diakonov Serhii (email: s.dyakonov@knubisoft.com)