-
Notifications
You must be signed in to change notification settings - Fork 253
Running Game Tests #338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Game Tests #338
Conversation
✅ Deploy Preview for nimble-elf-d9d491 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com>
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
Turns out I literally didn't even add gametest to the jvm arg... Ooops. This pr now works as expected. The only problem is that I couldn't get code group to work with the enhanced snippets, so the last two snippets are two snippets instead of one code group, which shouldn't be a big issue. |
its-miroma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I don't think we can use code groups with transclusions.
* upstream/main: Update rendering concepts page (FabricMC#362) "Setting up a Development Environment": VS Code (FabricMC#360) Running Game Tests In Github Actions (FabricMC#338) Items: Item Models (FabricMC#324) Call `.useBlockPrefixedTranslationKey()` (FabricMC#358) Clarify that `mod-id` placeholders must be customized (FabricMC#348) replace remaining mentions of tickDelta with tickProgress (FabricMC#361) Project location (FabricMC#326) improve the first items docs to state what's needed for item appearance, link fix (FabricMC#359)
* Add running game tests * Fix gradle working directory * Apply suggestions from code review Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> * Remove xvfb * Use Loom production run tasks * Fix production run task configuration * Add client game test to prodClient * Only add game test jvm arg --------- Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> (cherry picked from commit a01712f)
* Add running game tests * Fix gradle working directory * Apply suggestions from code review Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> * Remove xvfb * Use Loom production run tasks * Fix production run task configuration * Add client game test to prodClient * Only add game test jvm arg --------- Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> (cherry picked from commit a01712f)
* Add running game tests * Fix gradle working directory * Apply suggestions from code review Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> * Remove xvfb * Use Loom production run tasks * Fix production run task configuration * Add client game test to prodClient * Only add game test jvm arg --------- Co-authored-by: Miroma <136986257+its-miroma@users.noreply.github.com> (cherry picked from commit a01712f)
Adds instructions on how to run game tests locally and on github actions.