25w03a game tests #4385
Merged
25w03a game tests #4385
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
modmuss50
added
port
...est-api-v1/src/main/java/net/fabricmc/fabric/impl/gametest/FabricGameTestModInitializer.java
Outdated
Show resolved
Hide resolved
...c-gametest-api-v1/src/main/java/net/fabricmc/fabric/impl/gametest/TestAnnotationLocator.java
Outdated
Show resolved
Hide resolved
…gametest/TestAnnotationLocator.java Co-authored-by: Joseph Burton <[email protected]>
haykam821
suggested changes
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tottaly overhalled Game Test module to accomdate the changes made in 25w03a.
I have added back a
@GameTestthat functions almost the same as the previous one vanilla had. The new vanilla system makes it much harder to write a test than it was before. As there was a lot of value in the magic annotation and tests that are easy to write I think it makes sense to have something similar to what we had before.The options in the new Fabric provided
@GameTestannotation directly map the vanilla data driven options, removing the need to have a json file for each test function. Data driven tests will still work if you wish to use the vanilla system.The previous
fabric-api.gametestandfabric-api.gametest.report-filesystem properties work as they did before.fabric-api.gametest.filterandfabric-api.gametest.verifyhave been added that map directly to the vanilla gametest entrypoint options.Tests can still be ran/debuged from within a client using the
/testcommand. Structures can still be loaded from snbt files as before.