>>>>> Eric Lilja <[email protected]>: > The reactor strategy decides if a new container should be spawned per > method or per class. If I have a bunch of different tests in the same > class, I would not want to spawn the container more than once, if I > could avoid it, since it's expensive. The provisioned bundles etc are > typically defined in the @Configuration-method, so the set of > provisioned bundles is shared by all tests, regardless of reactor > strategy. It sounds like you want to re-use the container for the > tests in a given test class but tweak the provisioning between tests, > meaning you cannot rely on the shared @Configuration-method, but have > to also provision stuff in the test themselves.
No, provisioning once with @Configuration will be fine, if that actually loads the feature I'm adding. I just wasn't sure if @Configuration would work here, since the base class was different, and the example didn't use it, and I have never investigated how the setup of KarafTestSupport classes actually work. I thought maybe the installAndAssertFeature() function was necessary to load the feature? (but I have never investigated)
