Description of problem:
The BaseTestSetup class allows specification of required initializers,
 however, it does not use the init_requirements table to transitively
add the dependant intiializers. This makes it very tedious / error
prone to write unit tests for custom applications since you've got to
make sure you keep your unit test in sync with the <applcation>.load
file & all the dependant .load files.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a TestSetup class for 'Dublin Core' application
2. Add the 'com.arsdigita.london.cms.dublin.Initializer' class as a
requirement
3. Run the tests
  
Actual results:
Only Core & Dublin intiializers are run.

Expected results:
All dependant initializers are run, ie Core, CMS, AtoZ, Dublin, Terms,
Navigation, Util.


Additional info: