Terasology / Terasology/ModuleTestingEnvironment

World-building environment

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
3
Forks
17
PR merge metrics
No merged PRs in 30d

Description

In writing my first test using this module, I find myself spending a lot of time writing the code that sets up the environment appropriately (e.g., "ensure enough of the world is loaded, then put dirt here, here, and here"). It's not especially complicated for my particular use-case (yet), but I'm guessing that this sort of thing is a common enough need across enough different modules that I think it may be worth building an extension of ModuleTestingEnvironment that handles some of this for you.

I've been using this code as an example; @kaen has set up a DSL for concisely encoding the world template for the test. The extension I'm envisioning would be similar.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading ModuleTestingEnvironment and the example FlexibleMovementTestingEnvironment.java linked in the issue. Compare how the example encodes a world template and define the scope of a reusable extension. Done means a proposed environment extension can express common world setup concisely across modules.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.