Boundary Handling test case is flawed

[ColePoppleton]

The "Boids Update (Boundary Handling)" test directly sets the boid's position to (1000, 1000, 1000) before the update. While the update function does normalise it, this doesn't actually test the intended behaviour of the boids system correcting its position during a normal update cycle. It's testing the normalisation function more than the flocking behaviour at boundaries. Change the test case. Simulate several update cycles with the boundary handling in place to properly test that the boid system can deal with boundaries. Or, create a scenario where the forces acting on the boid naturally lead it to exceed the boundaries.