SplotyCode / MockBukkit

MockBukkit is a mocking framework for bukkit to allow the easy unit testing of Bukkit plugins.

---

---

MockBukkit is a framework that makes the unit testing of Bukkit plugins a whole lot easier. It aims to be provide complete mock implementation of CraftBukkit that can be completely controlled from a unit test.

📄 Table of contents

1. Usage
   • Adding MockBukkit via gradle
   • Adding MockBukkit via Maven
   • Using MockBukkit
2. Features
   • Mock Plugins
   • Mock Players
   • Mock Worlds
3. Troubleshooting (My tests are being skipped)
4. Discord server
5. Examples (See MockBukkit in action)

🔍 Usage

MockBukkit can easily be included in your project using either Maven or gradle.

Adding MockBukkit via Gradle

MockBukkit can easily be included in Gradle using the Maven Central and PaperMC repositories. Make sure to update the version as necessary.

repositories {
    mavenCentral()
    maven { url 'https://repo.papermc.io/repository/maven-public/' }
}

dependencies {
    testImplementation 'com.github.seeseemelk:MockBukkit-v1.19:2.29.0'
}

If you prefer to always have the latest Git version or need a specific commit/branch, you can always use JitPack as your maven repository:

repositories {
    maven { url 'https://jitpack.io' }
    maven { url 'https://repo.papermc.io/repository/maven-public/' }
}

dependencies {
    testImplementation 'com.github.MockBukkit:MockBukkit:v1.19-SNAPSHOT'
}

Note: use v1.13-SNAPSHOT to test a Bukkit 1.13 plugin or any other version if the branch exists. These branches will not be receiving patches actively, but any issues will be resolved and any pull requests on them will be accepted. This is because back-porting every single patch on every branch is incredibly time-consuming and slows down the development of MockBukkit.

Adding MockBukkit via Maven

MockBukkit can easily be included in Maven using the default Maven Central and PaperMC repositories. Make sure to update the version as necessary.

<repositories>
    <repository>
        <id>papermc</id>
        <url>https://repo.papermc.io/repository/maven-public/</url>
    </repository>
</repositories>

<dependencies>
  <dependency>
    <groupId>com.github.seeseemelk</groupId>
    <artifactId>MockBukkit-v1.19</artifactId>
    <version>2.29.0</version>
    <scope>test</scope>
  </dependency>
</dependencies>

The test scope is important here since you are likely to only be using MockBukkit during the test stage of your Maven lifecycle and not in your final product.

If you prefer to always have the latest Git version or need a specific commit/branch, you can always use JitPack as your maven repository:

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
    <repository>
        <id>papermc</id>
        <url>https://repo.papermc.io/repository/maven-public/</url>
    </repository>
</repositories>

<dependencies>
  <dependency>
    <groupId>com.github.MockBukkit</groupId>
    <artifactId>MockBukkit</artifactId>
    <version>v1.19-SNAPSHOT</version>
    <scope>test</scope>
  </dependency>
</dependencies>

Note: use v1.13-SNAPSHOT to test a Bukkit 1.13 plugin or any other version if the branch exists. These branches will not be receiving patches actively, but any issues will be resolved and any pull requests on them will be accepted. This is because back-porting every single patch on every branch is incredibly time-consuming and slows down the development of MockBukkit.

Using MockBukkit

In order to use MockBukkit the plugin to be tested needs an extra constructor and it has to be initialised before each test. The plugin will need both a default constructor and an extra one that will call a super constructor. Your plugins constructor will look like this if your plugin was called MyPlugin.

public class MyPlugin extends JavaPlugin
{
    public MyPlugin()
    {
        super();
    }

    protected MyPlugin(JavaPluginLoader loader, PluginDescriptionFile description, File dataFolder, File file)
    {
        super(loader, description, dataFolder, file);
    }
}

The plugin is now ready to be tested by MockBukkit. A plugin can be loaded in this initialiser block.

private ServerMock server;
private MyPlugin plugin;

@Before
public void setUp()
{
    server = MockBukkit.mock();
    plugin = MockBukkit.load(MyPlugin.class);
}

@After
public void tearDown()
{
    MockBukkit.unmock();
}

✨ Features

Mock Plugins

MockBukkit contains several functions that make the unit testing of Bukkit plugins a lot easier.

It is possible to create a mock plugin. This is useful when the plugin you are testing may be looking at other loaded plugins. The following piece of code creates a placeholder plugin that extends JavaPlugin.

MockPlugin plugin = MockBukkit.createMockPlugin()

Mock Players

MockBukkit makes it easy to create several mock players to use in unit testing. By running server.setPlayers(int numberOfPlayers) one can set the number of online players. From then on it's possible to get a certain player using server.getPlayer(int i).

An even easier way to create a player on the fly is by simply using

PlayerMock player = server.addPlayer();

A mock player also supports several simulated actions, such as damaging a block or even breaking it. This will fire all the required events and will remove the block if the events weren't cancelled.

Block block = ...;
player.simulateBlockBreak(block);

Mock Worlds

Another feature is the easy creation of mock worlds. One can make a superflat world using one simple command:

World world = new WorldMock(Material material, int heightUntilAir)

Using Material.DIRT and 3 as heightUntilAir will create a superflat world with a height of a 128. At y=0 everything will be Material.BEDROCK, and from 1 until 3 (inclusive) will be Material.DIRT and everything else will be Material.AIR. Each block is created the moment it is first accessed, so if only one block is only ever touched only one block will ever be created in-memory.

❓ My tests are being skipped!? (UnimplementedOperationException)

Sometimes your code may use a method that is not yet implemented in MockBukkit. When this happens MockBukkit will, instead of returning placeholder values, throw an UnimplementedOperationException. These exception extends AssumationException and will cause the test to be skipped.

These exceptions should just be ignored, though pull requests that add functionality to MockBukkit are always welcome! If you don't want to add the required methods yourself you can also request the method on the issues page.

🎧 Discord Server

You can also find us on discord by the way! If you need any help with MockBukkit or have a question regarding this project, feel free to join and connect with other members of the community.

🎉 Examples (See MockBukkit in action)

Several projects have utilized MockBukkit for their needs already. If you want to see some projects that are using MockBukkit right now, feel free to take a peak:

• Slimefun/Slimefun4 ( 400+ Unit Tests)
• lluiscamino/MultiverseHardcore ( 75+ Unit Tests)
• carelesshippo/SpectatorModeRewrite ( 50+ Unit Tests)
• JacksonChen666/treecapitator ( 30+ Unit Tests)
• axelrindle/PocketKnife (30+ Unit Tests)
• and more! (If you want to see your plugin here, open up an issue and we'll consider adding it)

You can also have a look at our documentation where we outline various examples and tricks on how to use MockBukkit already: https://mockbukkit.readthedocs.io/en/latest/index.html