Understanding Mock Testing: Unit Test Mocks, API Mocks, and Popular Tools

One evening I received a call from a tester who asked why the responses from my interface were identical for different test users in the daily environment; I explained that the interface data had been mocked, so it was returning mock data and the mock logic needed adjustment.

After hanging up, my curious girlfriend asked me about it.

Mock literally means "false" or "fake", but in object‑oriented programming it is usually translated as "simulation"; terms such as interface mock or mock object refer to simulated interfaces or objects.

In software development, mock techniques are typically used in two scenarios: unit testing and API testing.

Unit Test Mock

Initially, mocks were mainly applied in unit testing because the goal of a unit test is to focus on a specific "unit" while shielding external dependencies, which is where mock techniques become useful.

Mock techniques are also employed in many industrial testing scenarios, such as automotive crash testing.

Before a car is released, it undergoes crash tests to evaluate its crashworthiness and occupant protection; during these tests, specially designed dummies that mimic human weight, joint flexibility, and tissue strength are used.

Various types of dummies—adult, elderly, child, male, female—are employed to ensure comprehensive testing.

Thus, these dummies are essentially mock objects used to guarantee thorough and accurate testing.

The primary reason for using mock objects is that constructing real objects can be prohibitively expensive, so mocks are adopted instead.

Many tools help developers perform mock‑based unit testing, including EasyMock, jMock, Mockito, Unitils Mock, PowerMock, and JMockit.

The most commonly used among them are EasyMock ( https://easymock.org/ ), JMockit ( https://jmockit.github.io/index.html ) and Mockito ( https://site.mockito.org/ ), all of which are relatively easy to adopt.

A comparison chart of these tools is available on the JMockit website, as shown below:

Interface Mock

When testing a method that depends on an RPC remote service—whose return values can vary—we mock the external interface to robustly test our API across various boundary conditions.

By mocking the external interface, we can easily simulate normal responses, error responses, timeouts, and other scenarios for thorough testing.

Over the years, mock technology has expanded beyond unit testing, especially with the rise of micro‑services, where applications are highly decoupled and have many dependencies.

In this context, mock technology becomes especially important.

In many projects, teams develop concurrently, and downstream dependencies may be incomplete or lack certain edge cases, so mocking downstream interfaces is a practical solution.

For example, when integrating with Alipay during development, we often need to simulate cases such as expired protocols, insufficient balance, request timeouts, or non‑existent accounts by mocking the relevant APIs.

There are numerous API‑mocking tools available today, including RAP, YApi, Moco, and DOClever.

RAP

RAP is an interface management tool from the Alibaba team that provides convenient API documentation, mock, and export features. It can analyze interface structures, dynamically generate mock data, and verify real‑interface correctness, thereby improving collaboration efficiency.

The original project has been paused, but RAP2—a re‑implementation—continues development at https://github.com/thx/rap2-delos .

YApi

YApi, developed by the mobile architecture team at Qunar, is an open‑source project that offers elegant API management for developers, product managers, and testers, helping them easily create, publish, and maintain APIs. Official site: https://hellosean1025.github.io/yapi/ .

Moco

Moco is a tool for building mock servers; it supports both API‑mode (used within JUnit or other test frameworks) and standalone mode (running a JAR to start a mock service). Project: https://github.com/dreamhead/moco .

DOClever

DOClever is a free, open‑source visual API management tool that can analyze interface structures, validate correctness, and provide features such as API documentation, debugging, mocking, automated testing, and team collaboration. Official site: http://doclever.cn/controller/index/index.html .