Yves-Marie Haussonne 67113e897a feat(docker): add support for additional files in Dockerfile
Explanatory body:
This commit extends the Dockerfile and related scripts to support the inclusion of additional files during image build. The Dockerfile now accepts an `ADDITIONAL_FILES` argument, which can be passed during the build process. These additional files are copied into the container at specified paths. The changes also include updates to the `docker-compose.yaml` file and related scripts to handle the new `ADDITIONAL_FILES` argument appropriately during composition and execution.
2024-10-10 18:45:58 +02:00

Docker Test Harness for Minetest Mods

Overview

This mod provides an automated testing framework for Minetest mods by simulating player behavior on a Minetest server. It allows developers to create, register, and run tests to ensure the correct behavior of their mods in various scenarios.

Features

  • Test Registration: Easily register custom tests for your mod.
  • Player Behavior Simulation: Simulate player actions for automatic testing.
  • Modular Structure: Each test is associated with a specific mod and can be customized.
  • Area and Node Manipulation: Test areas can be defined, and node checks can be performed.
  • Test Context and State Management: Manage and track the progress of tests across multiple mods.

Prerequisite

The tests are run using Docker or Podman. Therefor you'll need to have either one of them installed.

Usage

This mod's goal is to provide a test framework for implementing tests for minetest mods.

  1. Declare test_harness as an optional dependencies for your mod

  2. copy the .util folder in your project

  3. copy the .util/.mod_env.json.tmpl to .mod_env.json at the root of your folder.

  4. adapt its content. Do not remove the test_harness dependency definition.

  5. The list of mods to test can be set in the additional_mods key. This list will be added to current_mod, if you add some mods, the list must start with a comma.

  6. customize the minetest server configuration by adding configuration values in the minetest_add_conf value. This must be a single string, with line returns if necessary.

  7. if necessary, customize the .util/Dockerfile if the previous means are not sufficients.

  8. In your source files (in the init.lua for example) add the following lines (or equivalent)

    if minetest.settings:get_bool("test_harness_run_tests", false) then
        dofile(minetest.get_modpath("my_mod").. "/test/init.lua")
    end
    
  9. In your test file(s), get an instance of the method allowing the registration of your tests:

    local register_test = test_harness.get_test_registrator("my_mod", my_mod.version_string)
    
  10. Register the test by calling register_test

  11. Run the test by lauching the run_tests.sh script. For example with Podman

    $ .util/run_tests.sh --podman -c 1
    

    See the available options with .util/run_tests.sh --help

Sources

License

Licensed under the AGPL (Affero General Public License).

Funding

This mod is published with funding from the NLNet Foundation.

Description
No description provided
Readme 97 KiB
Languages
Lua 61.1%
Dockerfile 20.1%
Shell 18.8%