Good ideas, but I think you are missing the point. This code is just hackish code to test some stuff, it's not meant to be extensible just yet. I could make it more abstract and move the logic up, but there is no point at this time.

If you mean in regards to the entire test suite, and are saying the game should keep track of the chunk manager and then pass it to the test suite or use it to initial the test suite, again that is good in the long run... but by the nature of testing all this code is transient. I may never need to test off the raw chunk data again, or I may need to constantly test off the chunk data... so it would be extreme premature abstraction to fix any of this system up.

Basically the test code should always be a bit rough, and abstracted later rather than sooner to avoid coupling it with code, which makes ripping it out (or more likely just ignoring it) harder. This is why the testExposure variable is nice, because it lets things expose their functionality without the requirement of the testing system needing them.