Hi, Thanks for the quick response! Yes that's exactly what we do, to elaborate more our setup has One BaseTestCase class where we configure the setup and teardown method in oder to allocate and deallocate the app object and other entities that every test case can benefit from. every TestClass inherits from this BaseTestCase and whenever required it makes use of the proper setup and teardown (by overriding the default and naturally invoking their super version) Is there a way that we can pursue to study what actually Xcode doesn't deallocate? Is there a reason why Xcode cannot guarantee that the memory would be deallocate per each test and not at the end of the entire test suite? I am asking not because I want to complain about it but because I am genuinely interested in understanding the rationale behind :) Hoping into an answer I wish you a good day!

I also experience the same problem: it makes the workflow quite unpleasant. See it with XCode 14.0, XCode 14.0.1, and with XCode 14.1 beta 3