Make sure TestingUtil.replaceComponent is only called after mock is fully configured

Some of our tests replace existing components. Unfortunately these could be replaced with mocks that aren't fully initialized until the next line. This can cause spurious test failures.