> One possibility I can think of currently is providing setters for the > controller's and having CorePrivate check if any of the > controller's is > already set to a valid value before creating a new instance of it. > > Does somebody have a better idea to this? Create a child CoreTest class used in your tests and provide setters in that. Kris Wong