Thanks for mentioning TestBase. I like the set() method to push values into
private fields.
You are certainly right about that @Parameter is about the interaction with
the container of the component and should be tested via an integration test.
Thanks again.
Stephan
-
--
http://www.caimit
My thoughts are that @Parameter annotation represents an integration
between the component and its immediate container or other part of the
system. @Parameter(required=true) failures will show up in
integration tests.
In the rare event that I unit test an individual component, I just use
the faci
Is there any recommended way of unit testing components that have @Parameter
annotations?
Of course I can add a setter to provide the parameter in my test but that
kind of defeats the purpose of @Parameter(required=true). I can call the
setter or not do it. If I don't call the setter, the test sh
