This is discussed quite a bit, and simply put, unit tests are totally inappropriate for something of this nature.
What we want are *integration* tests, and are going to be working to roll something out here.
It absolutely shouldn't be a unit test, because how in the world do you unit test ec2 with any reliability? The code ends up lying to itself.
I'm not interested in considering *units* for something that needs better testing here, though currently underway is some work to clean up things like Runner's code to allow unit testing at a cleaner level *there*.
The modules are going to be tested with playbooks and we hope to have something open-sourced soon in the coming months that provides some end-to-end testing of modules and playbook constructs, in real world scenarios using live systems, that is also user expandable via pull request.