For Java, in your testcases, you may want to use assertArrayEquals instead of assertEquals

Thank you, Making a copy of arr did the trick.

I didn't notice the feature of preloaded snippet. Thanks for pointing.

1. Moved the Point class to Preloaded snippet
2. Updated description

Resolved. Thank you for the pointer!

Noted. On it.

What is going on?

Time: 2708ms Passed: 0Failed: 4Exit Code: 1
Test Results:
Fixed_Tests
Basic_Tests
Expected: equal to [8.6667, 6.6667]
Actual: [8.6667, 6.6667]
Random_Tests
Moderate_Values
Expected: equal to [33, 37.3333]
Actual: [33, 37.3333]
High_Values
Expected: equal to [642.333, 895.667]
Actual: [642.333, 895.667]
Huge_Values
Expected: equal to [4697.33, 6422]
Actual: [4697.33, 6422]

Point # 3 doesn't make sense, logically & practically. Just having 2 non-opposite directions adjoining to eachother, doesn't reduce their effects overall unless you have distance in the play.

Then the task explanation needs updation...
if i follow {"NORTH","WEST","SOUTH","EAST"}, i am wasting my energy because it will bring me to the same point. The sequence doesn't matter...

Following test cases seem invalid;

1. Under Fixed_Tests - Input {"NORTH","WEST","SOUTH","EAST"} ; Expected says {"NORTH","WEST","SOUTH","EAST"}, but should be {}
2. Under Random_Tests - Input {"WEST","NORTH","EAST","EAST","EAST","SOUTH","EAST","NORTH","WEST","EAST","SOUTH","SOUTH","SOUTH","EAST","SOUTH","NORTH","WEST"}; Expected says {"WEST", "NORTH", "EAST", "EAST", "EAST", "SOUTH", "EAST", "SOUTH", "SOUTH"}, but should be {EAST", "EAST", "SOUTH", "EAST", "SOUTH"}

Please check other random test cases as well...

Was already marked as spoiler.

Thank you for the pointer.