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

test: fix connected components test #112

Merged
merged 2 commits into from
Jun 25, 2024

Conversation

JensSteenmetz
Copy link
Member

Description

This PR writes a new connected components test because the old one didn't work anymore.

Testability

Run ConnectedComponentsTest in the Unity Test Runner

Checklist

  • Set the proper pull request name
  • Merged main into your branch
  • Added a scene to the game for your changes (n/a)

Copy link
Contributor

@SilasPeters SilasPeters left a comment

Choose a reason for hiding this comment

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

I love that you used an interface here! You could perhaps even rewrite the complex ablit test (which also doesn't use query actions...)

Speaking of: could you perhaps use a query action to only walk towards the next key if that one exists? Might prevent the edge case I mentioned in a comment

Copy link

Copy link
Collaborator

@SSelinn SSelinn left a comment

Choose a reason for hiding this comment

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

LGTM

@JensSteenmetz JensSteenmetz merged commit 71f8927 into main Jun 25, 2024
3 checks passed
@JensSteenmetz JensSteenmetz deleted the test/fix-connected-components-test branch June 25, 2024 20:20
Copy link

🎉 This PR is included in version 3.34.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants