Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cryptic error messages about postconditions #131

Open
ijt opened this issue Jan 2, 2017 · 0 comments
Open

Cryptic error messages about postconditions #131

ijt opened this issue Jan 2, 2017 · 0 comments

Comments

@ijt
Copy link

ijt commented Jan 2, 2017

When a postcondition fails, PropEr should say which one failed. Instead it just says that some postcondition failed, so it's necessary to hunt around for which one. For example:

Shrinking .(1 time(s))
[{set,{var,2},{call,restdict,erase,[[97]]}}]
History: [{[],[]}]
State: []
Res: {postcondition,false}

Maybe it would help to return a descriptive string along with the boolean for the postcondition.
ijt added a commit to ijt/proper that referenced this issue Jan 2, 2017
@ijt
Allow an optional message in postconditions.
9d30b5a 
This makes it a lot easier to understand what went wrong when a test
fails.

This fixes proper-testing#131.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ijt