All feature-adding PRs need to have a test mod that demonstrates that the new feature works, and how to use it. A good test mod should:
-
be minimal. All that should be demonstrated is that the PR works correctly, nothing more. However test mods do not need to be minified, class and member names should be sensible. Nor is line count an issue, follow the Forge class formatting conventions when writing a test mod.
-
keep all classes in a single file. This can be achieved using nested classes.
-
follow 'best practices' at the time of creation. Test mods should be written using the same 'best practices' used for writing mods, with the exception of keeping all classes in a single file. For example a test mod written for a PR targeting 1.12 Forge should use
ObjectHolder
s &RegistryEvent
s.