> For the complete documentation index, see [llms.txt](https://testbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testbox.ortusbooks.com/v2.x-1/primers/testbox-xunit-primer/spies-and-mocking.md).

# Spies and Mocking

Please refer to our [MockBox](/v2.x-1/mocking/mockbox.md) section to take advantage of all the mocking and stubbing you can do. However, every BDD TestBundle has the following functions available to you for mocking and stubbing purposes:

* `makePublic( target, method, newName )` - Exposes private methods from objects as public methods
* `querySim( queryData )` - Simulate a query
* `getMockBox( [generationPath] )` - Get a reference to MockBox
* `createEmptyMock( [className], [object], [callLogging=true])` - Create an empty mock from a class or object
* `createMock( [className], [object], [clearMethods=false], [callLogging=true])` - Create a spy from an instance or class with call logging
* `prepareMock( object, [callLogging=true])` - Prepare an instance of an object for method spies with call logging
* `createStub( [callLogging=true], [extends], [implements])` - Create stub objects with call logging and optional inheritance trees and implementation methods
* `getProperty( target, name, [scope=variables], [defaultValue] )` - Get a property from an object in any scope


---

# 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:

```
GET https://testbox.ortusbooks.com/v2.x-1/primers/testbox-xunit-primer/spies-and-mocking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.