Add MeshRelation vertex group filtering tests#70
Merged
Conversation
This file contains hidden or 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
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.
Summary
Add comprehensive unit tests for the MeshRelation vertex group include/exclude filtering functionality, ensuring that vertex matching respects annotation-based group constraints.
Key Changes
New test file:
TestMeshRelation.fswith a single test caseMeshRelation: Include and Exclude vertex group trackingProject file updates:
TestMeshRelation.fsto compilation order in bothTest.MMManaged.fsprojandTest.MMManaged.dotnet.fsprojTest.MMManaged.dotnet.fsproj) with NUnit 3 test runner integration fordotnet testsupportImplementation Details
The test constructs minimal mesh objects with deliberately interleaved vertex positions to prove that group filtering logic (not spatial coincidence) drives the vertex matching behavior. Reference mesh has 8 vertices split into "Hat.Top" (indices 0-3) and "Hat.Bottom" (indices 4-7) groups; mod mesh vertices use Include/Exclude annotations to verify the filtering works correctly despite suboptimal spatial proximity.
https://claude.ai/code/session_01XXYvh4KUNLCobXoLrGUym6