This is likely a bugso please report this at http://github.com/guard/guard-rspec/issues/new along with as muchinformation as possible to reproduce this issue.
Coverage remained the same at 98.236% when pulling 0edd5df0a7b2fc05db5b3a3b89773f07349646a9 on robertjlooby:patch-1 into 1cf25c7127112c246b6e1a38208c32a6aee8a6c7 on guard:master.
Current message gets formatted like: