I had the same problem and sent a detailed message to the module author. The answer is that there is a bug in the test itself - the module is fine, so go ahead and force the install. The test bug will be fixed in a later release.
Update: Just noticed my version is 2.34, so not sure if this answer still applies.
---
It's all fine and dandy until someone has to look at the code.