[#289] Refactor Morley.Nettest errors types
Description
Problem: At the moment, expectFailure
accepts UnexpectedBalance
and UnexpectedClientSuccess
as args, even though it doesn't make sense to say:
expectBalance n `expectFailure` NettestUnexpectedBalance x
Solution: Split NettestFailure
into two types: one for errors thrown by the interpreter/client (that the user can expect to happen and handle), and another for errors thrown by cleveland when an assertion fails (which should not be caught, only displayed in the console).
Related issue(s)
Resolves #289 (closed)
✅ Checklist for your Merge Request
Related changes (conditional)
-
Tests (see short guidelines)
-
If I added new functionality, I added tests covering it. -
If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
-
-
Documentation
Stylistic guide (mandatory)
-
My commits comply with the following policy. -
My code complies with the style guide.