Skip to content
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

Add sample unit tests to the starter game template #46

Merged
merged 8 commits into from
Apr 25, 2024

Conversation

jerargus
Copy link
Contributor

@jerargus jerargus commented Apr 16, 2024

Add some sample unit test to the starter-game-template to demonstrate how testutils.TestFixture can be used to facilitate unit tests.

Specifically:

  • Add test for the Attack system to verify HP values are reduced.
  • Add test for the Attack system to verify invalid targets will result in a message error.
  • Add test for the Spawn system to verify players can be spawned.
  • Add a "recovery" system that will be run each time Cardinal is restarted.
  • Add a test for the recovery system to ensure the in-memory go object is re-populated when Cardinal is restarted.
  • Add an init system that creates some default players on tick 0.

Summary by CodeRabbit

  • New Features
    • Introduced a system to automatically spawn default players with specific attributes at the start of the game.
  • Bug Fixes
    • Standardized initial health points for players to enhance consistency in gameplay.
  • Tests
    • Added tests to ensure default players are spawned correctly and systems like player creation and attacks function as expected.

Copy link

coderabbitai bot commented Apr 16, 2024

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent update in the cardinal project introduces a more structured approach to initializing the game world, with a focus on player management. It enhances the system for spawning players, ensuring they start with predefined health and nicknames. The changes also include robust testing to verify the functionality of new and existing systems, ensuring that player creation and interactions are handled correctly from the start of the game.

Changes

Files Changes
.../init_test.go
.../system_test.go
Introduced new test cases to validate the creation and interaction of players, ensuring robustness in player management systems.
.../main.go
.../system/default_spawner.go
.../system/player_spawner.go
Enhanced player initialization and spawning mechanisms. Introduced MustInitWorld and SpawnDefaultPlayersSystem for systematic player creation with predefined attributes.

🐇✨
In the land of code, where the bits align,
A rabbit hopped, with a plan so fine.
"Let's spawn players," it said with glee,
"With health and names, as good as can be!"
Through tests and systems, with utmost care,
It crafted a world, quite unique and rare. 🌍🎮
🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Member

I think the whole non-ECS recovery stuff is way too implementation-specific and strays away from the purpose of the starter game template to serve as a scaffold for game projects.

If the goal of this is to provide examples or "cookbooks" for a specific edgecases, then we should do this in a separate examples repository.


// MustInitWorld registers all components, messages, queries, and systems. This initialization happens in a helper
// function so that this can be used directly in tests.
func MustInitWorld(w *cardinal.World) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want this, seems like an unnecessary hop

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's to ensure the test setup code matches the code that will eventually be deployed with world cardinal start. If we leave everything in the main function, I don't know how we would inject the test fixture world.

cardinal/system_test.go Outdated Show resolved Hide resolved
@jerargus
Copy link
Contributor Author

@coderabbitai review

@zulkhair
Copy link
Contributor

Looks like it would be better if added test target on makefile. so user can just run make test to run unit test

@jerargus
Copy link
Contributor Author

Looks like it would be better if added test target on makefile. so user can just run make test to run unit test

@zulkhair I added a make test target.

Copy link
Member

@smsunarto smsunarto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Add a github action to run the test

cardinal/system/default_spanwer.go Outdated Show resolved Hide resolved
@jerargus jerargus requested a review from smsunarto April 22, 2024 15:44
@jerargus jerargus merged commit 20306e2 into main Apr 25, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants