Hobo Test Philosophy

A test framework should fit into whatever workflow has been adopted by the team/individual.

Since the requirements for games vary so much a complete framework must provide all the necessary tools for any & all testing requirements.

While that creates a large ask for the project it enforces an idea that all tools provided by Hobo Test should work no matter that implementation (if it works in GM it should be testable; shouldn't matter if you add your keyboard pressed logic inside of Step or KeyPressed/Released Events)

While current support is only aimed at Windows I'd like to believe that all the win32 specific stuff being done could be replicated inside of GM on Mac (where there's a will there's a way)