mmonteleone/pavlov

Add support to check against error messages instead of objects

Opened this issue · 0 comments

I'm able to confirm that an exception is thrown with the throwsException extension. When I provide the string value of the expected error message, it fails to work. The code appears to be comparing objects with each other rather than the string value of the e.message.

I propose to support both the string value of messages and the expected error objects to be thrown.