@WouterJ have spoken briefly with @dbu and we agree that this would be better as a `getKernelConfig` that is called by the base test case. This prevents the dev from calling configure() at the wrong time(s), the name is also more purposful. (e.g. how do I configure the kernel? ah, theres a method called getKernelConfig .. )

Will merge and change, if you object we can always mess with it again later.