In reply to chr_sue:
This can work, but you are taking a hit on flexibility; consider this…
The component retrieves it’s configuration object via a dB get(); the config object’s members can be set to take a default value. The test can do the following actions to a component config object: randomize, manually populate values (from a parameters package), or do nothing (default behavior); the component will function in any of those 3 scenarios. A simple package import only supports static values.
Also at integration level, if you had multiple agents of the same type, I don’t see how they would know how to pull different sets parameters for a particular “configuration”.