Announcement Announcement Module
No announcement yet.
Testing/Validating config Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Testing/Validating config

    So let me ask this of everyone whose expirenced it.

    My group has moved towards making very simple componets that are easy to test thanks to dependency injection, but which are far more complicated to configure. One of the bad things about this is that although I can test all the *pieces* more effectively, its often harder to get an idea if the *whole* is working correctly.

    As an example, an application containing a dozen or more beans has enough configuration that a typo can show up and isn't realized until deployment time. All unit tests pass fine because they don't involve configuration, and as far as I know theres no sanity checking configuration until the last minute.

    Has anyone got a good way to deal with this?

  • #2
    Configuration issues usually turn up in our integration/system testing.


    • #3
      I extract out all the expensive/platform specific beans into their own config files and then during testing instantiate every other bean (plus placeholders), so for example, I might have a config file for the datasource (productionDataSource-context.xml and localDataSource-context.xml).