Find "leaking" items in test execution

[m-Schlitzer]

As it is now, the items created on the server by the tests remain there and fill up the storage.
tear_down() should clean that up, which it only does with resources acquired by curl_global_init, by calling curl_global_cleanup().

[bkircher]

Maybe we can purge the entire mailbox, even remove it entirely in global tear-down and create a new one in global set-up?

[bkircher]

Well, OTOH, each individual test case should clean-up after itself. Can you figure out which test case does leave everything around and why?

[m-Schlitzer]

Will do and update when I know more. Wouldn't this have a high impact on the test performance?

[bkircher]

Wouldn't this have a high impact on test performance?

Why? All test cases clean-up in TearDown() methods already. And test execution is still okay, absolutely bearable, IMO.

[m-Schlitzer]

Since it's only tests it won't be too bad I suppose. The contacts and tasks that are created are the ones that remain on the server. I'll check out how I can clean them up with tear_down()

[bkircher]

I'll check out how I can clean them up with tear_down()

Thank you. Keep in mind to search for the test cases that create these items first. The items should be removed by the TearDown() method of the individual test case or using a on_scope_exit scope guard if they are not created in a SetUp().

Removing or cleaning-up the entire mailbox in a global tear-down should be done only when all else has failed.