Feature Request: Expected vs Actual Debugging

[jarrodparkes]

When running a spec/contract test, it would be extremely beneficial to see the expected (passing) criteria against the actual. This could be shown via a flag, method, etc.

For example:

**Expected**
price: int, nullable

**Actual**
price: int

^^ And if this coincides with a failure, then it is pretty clear what the developer needs to do.

Right now, it is very difficult to grok what goes wrong when a contract test fails. I think this would be a good step in the right direction. Its importance only grows as the expected criteria gets more complex (think a response with dozens of fields).

[jarrodparkes]

Been thinking some more about this. Using a "diff" approach could make this even more concise and helpful