Simple transformers testing test

To create simple transformers test case you need to extend AbstractSubsystemBaseTest:

public class MyTransformersTestCase extends AbstractSubsystemBaseTest {
    public MyTransformersTestCase() {
        super("mysubsystem", new MySubsystemExtension());
    }
    @Override
    protected String getSubsystemXml() throws IOException {
        return readResource("testing.xml");
    }
}

Now you can add transformation test. The test will load a testing XML file into latest subsystem and will try to initialize legacy subsystem from it.

At first, lets specify target version of transformation. The frameworks requires to specify version of the controller using ModelTestControllerVersion enum and version of the model of the tested subsystem (ModelVersion as specified in the transformers). In following example we will transform to the subsystem model version default to the given controller version:

ModelTestControllerVersion controller = ModelTestControllerVersion.EAP_7_1_0;
ModelVersion subsystemModelVersion = controller.getSubsystemModelVersion("elytron");

The AbstractSubsystemBaseTest provides a method to obtain KernelServicesBuilder allowing to boot up controller for latest version of the subsystem:

KernelServicesBuilder builder = createKernelServicesBuilder(AdditionalInitialization.MANAGEMENT);

The builder will be used to boot up the old version of controller too. Take a note the old subsystem is downloaded from Maven repository:

builder.createLegacyKernelServicesBuilder(AdditionalInitialization.MANAGEMENT, controller, subsystemModelVersion)
       .addMavenResourceURL("org.wildfly.core:wildfly-elytron-integration:4.0.0.Final");

Now you can finish the builder and verify that both controllers has booted up successfully:

KernelServices services = builder.build();
assertTrue(services.isSuccessfulBoot());
assertTrue(services.getLegacyServices(subsystemModelVersion).isSuccessfulBoot());

The model parsed by latest controller from XML provided by{{getSubsystemXml()}} is now already transformed and used by the legacy controller. The framework provides method to check that both models are the same and valid:

checkSubsystemModelTransformation(services, subsystemModelVersion, null, true);

Testing of rejecting rules

Part of the transformers are also rejecting rules, which needs to be tested too. Lets image we have a new attribute "flushed" which cannot be part of the legacy model. To test it will be rejected, we need to write and XML configuration containing it, to parse it and to try to transform it:

List<ModelNode> operations = builder.parseXml(
    "<subsystem xmlns=\"urn:wildfly:mysubsystem:3.0\">\n" +
    "    <my-resource name=\"test\" flushed=\"true\"/>\n" +
    "</subsystem>");

ModelTestUtils.checkFailedTransformedBootOperations(services, subsystemModelVersion, operations, new FailedOperationTransformationConfig()
    .addFailedAttribute(myResourceTestPathAddress,
        new FailedOperationTransformationConfig.NewAttributesConfig("flushed"))
);

Util of testing subsystem will check that ALL listed attributes (and nothing else) was rejected.

Be aware the test framework use FailedOperationTransformationConfig to fix the model to continue checking following failures.
The NewAttributesConfig will ensure the attribute "flushed" will be undefined after its failing.
If you are checking rejecting subattribute in complex attribute, the whole attribute will be undefined, which will cause operation failure if the complex attribute was required. You need to use REJECTED_RESOURCE config in such case - the whole resource adding operation will be removed before continuing the evaluation.