@silly-article-89931: That problem looks familiar. I think you have to add some extra code to your unit test to handle this... Let me look.