Make WordPress Core

Opened 3 years ago

Last modified 2 years ago

#53011 new task (blessed)

Tests: review all setUp() and tearDown()

Reported by: jrf's profile jrf Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: has-patch has-unit-tests
Focuses: docs, performance, coding-standards Cc:


The setUpBeforeClass(), setUp(), tearDown() and tearDownAfterClass() (and the WP test suite native variants of these) methods in test classes are used to set up fixtures which will be used by all tests in the test class.

Also see:

For tests to properly be able to test just and only that which is being tested, we need to make sure that changes to the "global state" are undone after each test.

This includes:

  • Changes to variables in $GLOBALS, changes to global variables via global $var_name.
  • Changes to superglobals, like $_GET, $_POST or $_REQUEST.
  • Filters being hooked or unhooked to WordPress using add_filter(), remove_filter(), add_action(), remove_action() (and all their variations) calls in setUp() methods - or in the tests themselves.
  • Changes in the file system - file being created by a test should be deleted after the test.
  • And more contentiously: changes in the database ought to be undone after a test as well. This doesn't mean that any posts being created for a test and only being used by that test need to be deleted, but it does mean that any schema changes, any new tables created etc should be undone after the test.

At this time, the WP Core test suite does not consistently "undo" changes to the global state for each test, as @hellofromTonya and me found while reviewing tests for an unrelated patch.

We would like to recommend a full review of the test suite for best practices regarding global state resetting after each test.

Note: if a "reset" action is being done within the code of a test function, it may not get executed when the tests fails. To that end, these type of "reset"s should generally be done in the tearDown(), even when they only apply to one test in the test class.
The "reset", in that case, should be accompanied by a comment pointing to the test to which it applies.

Change History (8)

#1 @johnbillion
3 years ago

Recent work that was done relating to this: [50449], [50450], [50463].

#2 @johnbillion
3 years ago

  • Version trunk deleted

#3 @jrf
3 years ago

@johnbillion Thanks for linking those changesets. Those are good improvements, glad to see those were already made 💪👍 Looks like those all sprang from #52625.

#4 @jrf
3 years ago

Related #53746, #50209

When reviewing the changes proposed in #53746, it also became very clear that setUp() and tearDown() are incorrectly used at this time in the WP test suite.

setUp() should prepare the environment for the tests.
tearDown() should bring the environment back to the default state.

At this time, a lot of "bring back to default state" is done in setUp(), making the test suite inherently unstable.

A review of, and improvement to this should be included in this ticket.

This ticket was mentioned in PR #1642 on WordPress/wordpress-develop by hellofromtonya.

3 years ago

  • Keywords has-patch has-unit-tests added

Tests: Removes unnecessary _set_cron_array() from tear_down()`.

The 'cron' option is reset as part of the test suite's DB transaction. Resetting it within each test's tear_down() is unnecessary and redundant.

Trac ticket:

hellofromtonya commented on PR #1642:

3 years ago

Hmm in further investigation, the parent tear_down() is not resetting the 'cron' object as expected. Changing this PR back to WIP as it needs more investigation.

Note: See TracTickets for help on using tickets.