ModuleTestingEnvironment isn't a module in the sense that it's something you load during your play session, even for test purposes.
It's a library you can use with your test framework to provide a test harness for automated headless testing of events running in a Terasology engine.
I'd like to reclassify this from "terasology module" to a library we use as a testImplementation dependency.
The fixtures (DummyWorldGenerator and such) do contain some things that probably do need to be registered with the engine, so maybe that means this does still need to provide a module in some sense. There are some details to figure out there.
keturn
commented
2 years ago
ModuleTestingEnvironment isn't a module in the sense that it's something you load during your play session, even for test purposes.
It's a library you can use with your test framework to provide a test harness for automated headless testing of events running in a Terasology engine.
I'd like to reclassify this from "terasology module" to a library we use as a
testImplementationdependency.The fixtures (DummyWorldGenerator and such) do contain some things that probably do need to be registered with the engine, so maybe that means this does still need to provide a module in some sense. There are some details to figure out there.