Terasology / Terasology/ModuleTestingEnvironment
add ability to use a WorldGenerator defined in src/test (not src/main)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
MTE has a way to specify which world generator should be used: The @UseWorldGenerator annotation.
That works fine for WorldGenerators defined in the module or dependencies of the module, but it does not currently allow you to define a WorldGenerator in your classes under the src/test sources.
It would be nice to be able to do so. With the current limitation, any world generators defined for testing (i.e. to make worlds that have very specific properties in predicable places, unlike the random worlds for game modes) will show up mixed in with the other world types that are provided for gameplay.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/main/java/org/terasology/moduletestingenvironment/extension/UseWorldGenerator.java and trace how annotated WorldGenerators are discovered from module and dependency classes. Compare that path with test sources, using the original discussion for context; done means a generator under src/test can be selected for tests without appearing among gameplay world types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100