Title: wp cron test
Published: February 5, 2018
Last modified: May 23, 2026

---

# 󠀁[wp cron test ](https://developer.wordpress.org/cli/commands/cron/test/)󠁿

Tests the WP Cron spawning system and reports back its status.

## In this article

 * [Examples](https://developer.wordpress.org/cli/commands/cron/test/?output_format=md#examples)
 * [Global Parameters](https://developer.wordpress.org/cli/commands/cron/test/?output_format=md#global-parameters)

[ Back to top](https://developer.wordpress.org/cli/commands/cron/test/?output_format=md#wp--skip-link--target)

 [ ⌊GitHub⌉ ](https://github.com/wp-cli/cron-command)

 [ View Open Issues (0) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Acron-test+sort%3Aupdated-desc+org%3Awp-cli+is%3Aopen)
[ View Closed Issues (5) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Acron-test+sort%3Aupdated-desc+org%3Awp-cli+is%3Aclosed)
[Create New Issue](https://github.com/wp-cli/cron-command/issues/new)

This command tests the spawning system by performing the following steps:

 * Checks to see if the `DISABLE_WP_CRON` constant is set; errors if true because
   WP-Cron is disabled.
 * Checks to see if the `ALTERNATE_WP_CRON` constant is set; warns if true.
 * Attempts to spawn WP-Cron over HTTP; warns if non 200 response code is returned.

### 󠀁[Examples](https://developer.wordpress.org/cli/commands/cron/test/?output_format=md#examples)󠁿

    ```
    # Cron test runs successfully.
    $ wp cron test
    Success: WP-Cron spawning is working as expected.
    ```

### 󠀁[Global Parameters](https://developer.wordpress.org/cli/commands/cron/test/?output_format=md#global-parameters)󠁿

 These [global parameters](https://make.wordpress.org/cli/handbook/config/) have
the same behavior across all commands and affect how WP-CLI interacts with WordPress.

  |  **Argument** |  **Description** |  
   |  `--path=<path>` |  Path to the WordPress files. |  
 |  `--url=<url>` |  Pretend request came from given URL. In multisite, this argument is how the target site is specified. |  
 |  `--ssh=[<scheme>:][<user>@]<host\|container>[:<port>][<path>]` |  Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”). |  
 |  `--http=<http>` |  Perform operation against a remote WordPress installation over HTTP. |  
 |  `--user=<id\|login\|email>` |  Set the WordPress user. |  
 |  `--skip-plugins[=<plugins>]` |  Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded. |  
 |  `--skip-themes[=<themes>]` |  Skip loading all themes, or a comma-separated list of themes. |  
 |  `--skip-packages` |  Skip loading all installed packages. |  
 |  `--require=<path>` |  Load PHP file before running the command (may be used more than once). |  
 |  `--exec=<php-code>` |  Execute PHP code before running the command (may be used more than once). |  
 |  `--context=<context>` |  Load WordPress in a given context. |  
 |  `--[no-]color` |  Whether to colorize the output. |  
 |  `--debug[=<group>]` |  Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help. |  
 |  `--prompt[=<assoc>]` |  Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values. |  
 |  `--quiet` |  Suppress informational messages. |

 _Command documentation is regenerated at every release. To add or update an example,
please submit a pull request against the corresponding part of the codebase._