This is another dependency issue I'm afraid. While instigating the new model builders I notice that several of the assembly-xml unit tests now fail. This is because these tests use the builders but with invalid composites. The composites have many implementations and bindings that are/can not be referenced by assembly-xml. This leads to null implementations and empty binding collections that the builders are not expecting.
I added some null checks to allow the tests to run and even then I have to comment out the policy promotion one (my null tests are not in precisely the same place as in the old builders). However this doesn't feel like the right approach to me. I'd rather have tests in assembly-xml that are designed to run there properly without needing special checks in the builders. Thoughts? Simon
