What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
adds a unit test for the GuttingFishSorting.cs
What is the current behavior? (You can also link to an open issue here)
the test automatically fails in this branch but should not be a problem if #485 is merged aswell
What is the new behavior? (if this is a feature change)
altered GuttingFishSorting.cs to make sure the collision does not register the same fish as sorted twice similar to how the DiscardBadFish.cs script does, and then testing that it works properly with a test.
Tests the GuttingFishSorting.cs by running the sorting method (which is now a bool) against all possible inputs and checking that only the expected input returns true
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) adds a unit test for the GuttingFishSorting.cs
What is the current behavior? (You can also link to an open issue here) the test automatically fails in this branch but should not be a problem if #485 is merged aswell
What is the new behavior? (if this is a feature change) altered GuttingFishSorting.cs to make sure the collision does not register the same fish as sorted twice similar to how the DiscardBadFish.cs script does, and then testing that it works properly with a test. Tests the GuttingFishSorting.cs by running the sorting method (which is now a bool) against all possible inputs and checking that only the expected input returns true
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
485 should be merged first