-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving testing framework and adding the capability to predicate on resulting log #450
Conversation
Is there another branch than main to use as a target in Github for this PR in order to improve readability of the diff and only show the changes related to this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great and long overdue overhaul of the testing module, that is sane and straightforward.
@@ -279,6 +114,9 @@ instance IsProp Bool where | |||
testConjoin = and | |||
testDisjoin = or | |||
|
|||
-- * Extra HUnit assertions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are those exactly. Do we ever need them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are used in some testing modules. They used to be in some sort of a utility module in tests which was removed a while ago.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. What do you think about those?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they are here for a lack of a better location, but they do not create any harm.
When we use predicates on results of traces, we need to take into account the logging that happens during the run. This is what this PR aims to achieve.