Terasology / Terasology/ModuleTestingEnvironment

add ability to use assets defined in src/test

Open
#71 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Size: M Type: Improvement
Dominant language
Java
Stars
3
Forks
17
PR merge metrics
No merged PRs in 30d

Description

I was looking at writing tests for DynamicCities. It has systems that depend heavily on prefab assets for configuration. Sure, we can change those things to add programmatic interfaces for configuration as well, but it's a reasonable design: Configuration of these things should be data-driven, and the way modules load data is through the asset manager.

But I don't want the assets I define for specific test scenarios mixed in with all the other assets meant for gameplay.

[original discussion]

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 examining how tests under src/test currently obtain assets through the asset manager, with DynamicCities as the motivating case. Determine how test-specific prefab assets can remain separate from gameplay assets, then verify that a test can define and load such an asset without changing the production asset set.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.