> For the complete documentation index, see [llms.txt](https://wp-mock.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp-mock.gitbook.io/documentation/usage/mocking-wp-constants.md).

# Mocking WordPress Constants

Certain constants need to be mocked, otherwise various WordPress functions will attempt to include files that just don't exist.

For example, nearly all uses of the `WP_Http` API require first including:

```
ABSPATH . WPINC . '/class-http.php'
```

If these constants are not set, and files do not exist at the location they specify, functions referencing them will produce a fatal error.

By default, WP\_Mock will [mock the following constants](https://github.com/10up/wp_mock/blob/trunk/docs/usage/php/WP_Mock/API/constant-mocks.php):

| Constant         | Default mocked value                   |
| ---------------- | -------------------------------------- |
| `WP_CONTENT_DIR` | `__DIR__ . '/dummy-files'`             |
| `ABSPATH`        | `''`                                   |
| `WPINC`          | `__DIR__ . '/dummy-files/wp-includes'` |
| `EZSQL_VERSION`  | `'WP1.25'`                             |
| `OBJECT`         | `'OBJECT'`                             |
| `Object`         | `'OBJECT'`                             |
| `object`         | `'OBJECT'`                             |
| `OBJECT_K`       | `'OBJECT_K'`                           |
| `ARRAY_A`        | `'ARRAY_A'`                            |
| `ARRAY_N`        | `'ARRAY_N'`                            |

WP\_Mock provides a few dummy files, located in the `./php/WP_Mock/API/dummy-files/` directory. These files are used to mock the `WP_CONTENT_DIR` and `WPINC` constants, as shown in the table above.

The `! defined` check is used for all constants, so that individual test environments can override the normal default by setting constants in a bootstrap configuration file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wp-mock.gitbook.io/documentation/usage/mocking-wp-constants.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.