YamlExtensionTestCase uses hardcoded files (see test.xml and testWithCli.xml under wildfly-core/testsuite/manualmode/src/test/resources/org/jboss/as/test/manualmode/management/persistence) that represent the expected server configurations we should have after applying the configuration via yaml.

These files need to be maintained if we change the default server configuration in a different Jira. See for example https://github.com/wildfly/wildfly-core/pull/5764 where adding a new log configuration requires the modification of the YamlExtensionTestCase.

To avoid this maintenance, we could generate these configurations using a different method, for example

1. Applying standard management operations.
2. Grabbing a copy of the generate files
3. Discard them or rollback the changes
4. Using the grabbed files as a source of trust to compare with the yaml configuration method.