The primary goal here is to be able to plug into alternative implementations of configuration providers to ensure tests are run in the fixed setup independent of system setup (e.g. use own cache, etc.). Config should probably be appcontext specific instead of being static. This simplifies test execution in the same VM. It should unify details coming from various sources including files and registry.

We could write code like:
   Deployment.getConfig().getCacheDir();
to get values.

And something like
   TestConfig t = new TestConfig();
   t.setCacheDir("xxxx");
   Deployment.setConfigStub(t);
to customize config in the test.

We also want to make Config API more clean and flexible but this partially can be addressed using other CRs.