> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/containers-and-orchestration/containerisation/container-images/popular-container-images/mocking-and-testing-tools.md).

# Mocking & Testing Tools

## About

Containers for tools like MockServer and WireMock used to simulate APIs, dependencies, or external services in a controlled environment. They are crucial for integration and contract testing, especially in microservice architectures.

## **MockServer 5.15.0**

MockServer is a powerful tool for mocking and testing HTTP and HTTPS APIs. It allows developers to simulate RESTful services, HTTP endpoints, and complex integration behaviors. The `mockserver:mockserver-5.15.0` image is a stable release ideal for local testing, CI pipelines, or integration with tools like Testcontainers.

**Docker Pull Command:**

```bash
docker pull --platform linux/amd64 mockserver/mockserver:mockserver-5.15.0
```

**Basic Usage:**

```bash
docker run -d \
  -p 1080:1080 \
  mockserver/mockserver:mockserver-5.15.0
```

**Notes:**

* REST API is available on port `1080` for setting up expectations and verifying requests
* Can be used in automated tests with Java libraries or Postman scripts
* Compatible with Testcontainers via `org.testcontainers:mockserver`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/containers-and-orchestration/containerisation/container-images/popular-container-images/mocking-and-testing-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.