@Test
    void requireThatValidatorHandlesVespaModel() {
        List<ConfigChangeAction> changes = getConfigChanges(
                createVespaModel(createQrStartConfigSegment(true, 2096)),
                createVespaModel(createQrStartConfigSegment(false, 2096))
        );
        assertEquals(4, changes.size());
        assertComponentsEquals(changes, "default/container.0", 0);
        assertComponentsEquals(changes, "admin/logs/0", 1);
        assertComponentsEquals(changes, "admin/cluster-controllers/0", 2);
        assertComponentsEquals(changes, "admin/metrics/localhost", 3);
    }
NOTE: This test method has the following assumptions about the {@link com.yahoo.vespa.model.VespaModel}:
   1) verbosegc and heapsize in qr-start.def is marked with restart.
   2) {@link com.yahoo.vespa.model.container.Container} class has QrStartConfig listed in its
      {@link com.yahoo.vespa.model.application.validation.RestartConfigs} attribute.
   3) That the config ids for the container services have a specific value.

This test will to a certain degree ensure that the annotations in the VespaModel is correctly applied.
config-model/src/test/java/com/yahoo/vespa/model/application/validation/change/ConfigValueChangeValidatorTest.java