public interface RelativeEntityTestCase extends TargetableTestComponent
For example, to run tests against a named child of an entity:
services
- id: app
brooklyn.children:
id: child-id
- id: test-case
brooklyn.config:
anchor: $brooklyn:component("app").descendant("child-id")
The anchor entity is resolved from the anchor, target or
targetId, in order of preference. The latter two are useful when using
the test with with entities like LoopOverGroupMembersTestCase. Values for
target will be overwritten with the resolved entity so child test
cases work as expected.Entity.AdjunctSupport<T extends EntityAdjunct>, Entity.EnricherSupport, Entity.GroupSupport, Entity.PolicySupport, Entity.SensorSupportBrooklynObject.RelationSupport<T extends BrooklynObject>, BrooklynObject.SubscriptionSupport, BrooklynObject.TagSupportConfigurable.ConfigurationSupportStartable.RestartEffectorBody, Startable.StartEffectorBody, Startable.StopEffectorBody| Modifier and Type | Field and Description |
|---|---|
static AttributeSensorAndConfigKey<Entity,Entity> |
ANCHOR |
static ConfigKey<DslComponent> |
COMPONENT |
TARGET_ENTITY, TARGET_ENTITY_ID, TARGET_ENTITY_NAME, TARGET_ENTITY_TYPE, TARGET_ID, TARGET_RESOLUTION_TIMEOUTRESTART, SERVICE_UP, START, STOPresolveTargetaddChild, addChild, addFeed, clearParent, enrichers, getApplication, getApplicationId, getAttribute, getChildren, getConfig, getCreationTime, getDisplayName, getEntityType, getIconUrl, getId, getLocations, getParent, groups, invoke, policies, relations, removeChild, sensors, setDisplayName, setParentgetCatalogItemId, getCatalogItemIdSearchPath, subscriptions, tagsconfig, getConfigstatic final AttributeSensorAndConfigKey<Entity,Entity> ANCHOR
static final ConfigKey<DslComponent> COMPONENT