Unmocked

Unmocked is a term used in software development, particularly in the context of testing, to describe a situation where a piece of code is executed without the use of mock objects or test doubles. In unit testing, developers often replace external dependencies with mock objects to isolate the code under test and control its behavior. When a test is "unmocked," it means that the actual dependencies are present and interacting as they would in a real-world scenario.

This approach is often referred to as integration testing or end-to-end testing, depending on the scope. Running tests unmocked can provide a more realistic assessment of how different components of a system interact. It helps identify issues that might not arise when dependencies are mocked, such as problems with data serialization, network communication, or database interactions.

However, unmocked tests can be slower, more brittle, and require a more complex setup to run. They might also depend on external resources like databases or network services, which can make them harder to execute in automated continuous integration pipelines. The decision to use mocked or unmocked tests depends on the specific goals of the testing strategy and the trade-offs between realism and testability.