In PHPUnit test classes, parent::tearDown() should be the last thing done in tearDown() methods.

`WP_UnitTestCase::tearDown()` restores the test environment to the default
conditions, including rolling back the MySQL transaction that the test takes
place in, resetting globals, and unhooking test-specific filters. As such, all
teardown routines for specific tests should happen before the parent class's
`tearDown()` method is called. Failure to do so can cause database locks on
certain configurations, among other problems.

See #31537.

git-svn-id: https://develop.svn.wordpress.org/trunk@31622 602fd350-edb4-49c9-b593-d223f7449a82

tests/phpunit/tests/customize/manager.php

@@ -16,9 +16,9 @@ class Tests_WP_Customize_Manager extends WP_UnitTestCase {
 	}
 
 	function tearDown() {
-		parent::tearDown();
 		$this->manager = null;
 		unset( $GLOBALS['wp_customize'] );
+		parent::tearDown();
 	}
 
 	/**

tests/phpunit/tests/customize/setting.php

@@ -26,9 +26,9 @@ class Tests_WP_Customize_Setting extends WP_UnitTestCase {
 	}
 
 	function tearDown() {
-		parent::tearDown();
 		$this->manager = null;
 		unset( $GLOBALS['wp_customize'] );
+		parent::tearDown();
 	}
 
 	function test_constructor_without_args() {

tests/phpunit/tests/customize/widgets.php

@@ -35,10 +35,10 @@ class Tests_WP_Customize_Widgets extends WP_UnitTestCase {
 	}
 
 	function tearDown() {
-		parent::tearDown();
 		$this->manager = null;
 		unset( $GLOBALS['wp_customize'] );
 		unset( $GLOBALS['wp_scripts'] );
+		parent::tearDown();
 	}
 
 	function set_customized_post_data( $customized ) {