Currently the test methods do not call the key methods from map_env i.e. step, reset, init but generate the effect of them by calling sub-pieces of each of these methods. This introduces serious potential for error and needs immediate refactoring.
I can't call any of these methods because they spawn apples in a stochastic way.
Option 1: disable the stochasticity.
Option 2: disable the spawning (somehow)
Currently the test methods do not call the key methods from map_env i.e. step, reset, init but generate the effect of them by calling sub-pieces of each of these methods. This introduces serious potential for error and needs immediate refactoring.