[7.0] Write functional tests to validate consumable results

Open
#1,028 1 comment 0 reactions 2 assignees View on GitHub

@LexManos is already working on this.

Since Dec 24, 2025.

Assessment

This issue has not been assessed yet.

Description

ForgeGradle 7.0 and later need to have functional tests written for it to avoid regressions that may be caused by updates to the Minecraft Mavenizer, Slime Launcher or ForgeGradle itself.

This is especially important in terms of how ForgeGradle handles Mixin and its compatibility with projects. Earlier incidents (#1026 is not the only one) have proven that there are unbearably high expectations on ForgeGradle to always remain functional with regards to Mixin and its usage in projects and at runtime. Any potential regressions to Mixin functionality in ForgeGradle threaten to be a massive headache moving forward. This needs to be addressed and tests need to be made.

[!NOTE]
Gradle's User Guide has a page on Testing Plugins. This will serve as a good starting point to write tests for all of our projects, including ForgeGradle, though all of our projects should get the same love with regards to tests and buildscript cleanliness.

Dominant language
Java
Stars
574
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
1

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.

More from MinecraftForge/ForgeGradle

All issues in MinecraftForge/ForgeGradle

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.