Currently crud and transaction spec tests have matchers which perform many comparisons and yield a true/false value, which is then passed to rspec. When any of the comparisons fail, the respective test fails, but there is no diagnostics as to which of the comparisons actually failed, and why.

Instead of using matchers like this a more helpful implementation will be to perform rspec assertions throughout the verification code so that any differences are flagged with the expected/actual values as well as context for the operation that was being verified.