This was encountered whilst developing tests for the metadata component's resource input panel. This has not yet been reduced to a standalone test case, but the symptoms were odd - in one order the test stalls at sequence point 2 of 2, and in the other order, the test reaches 3 of 2 but then fails with "fixture is undefined". Discussion was on IRC at https://botbot.me/freenode/fluid-work/2014-04-30/

Branch is checked in for investigation at https://github.com/jobara/metadata/tree/FLOE-116-broken-IoCTestingSequence