diff --git a/tests/lib/adler_testcase.php b/tests/lib/adler_testcase.php
index fcfaf67..6903db4 100644
--- a/tests/lib/adler_testcase.php
+++ b/tests/lib/adler_testcase.php
@@ -28,16 +28,7 @@ public function setUp(): void {
     public function tearDown(): void {
         parent::tearDown();
 
-        // Moodle thinks debugging messages should be tested (check for debugging messages in unit tests).
-        // Imho this is very bad practice, because devs should be encouraged to provide additional Information
-        // for debugging. Checking for log messages in tests provides huge additional effort (e.g. tests will fail because
-        // a message was changed / an additional one was added / ...). Because logging should NEVER affect the
-        // functionality of the code, this is completely unnecessary. Where this leads can be perfectly seen in all
-        // moodle code: Things work or do not work and there is no feedback on that. Often things return null if successfully
-        // and if nothing happened (also categorized as successful), but no feedback is available which of both cases happened.
-        // Users and devs very often can't know why something does not work.
-        // If something went wrong either the code should handle the problem or it should throw an exception.
-        $this->resetDebugging();
+        Mockery::close();
     }
 }