Skip to content

Conversation

@ijt
Copy link

@ijt ijt commented Jan 2, 2017

ijt added 3 commits January 1, 2017 19:18
This makes it a lot easier to understand what went wrong when a test
fails.

This fixes proper-testing#131.
This was found by a dialyzer run:

https://travis-ci.org/manopapad/proper/jobs/188348558
dialyzer -n -nn --plt .plt/proper_plt -Wunmatched_returns ebin
@ijt ijt changed the title Fix issue #132: Pretty print call sequences. Fix issues #131 and #132 to get more readable output on failures Jan 2, 2017
ijt added 2 commits January 7, 2017 14:00
Instead of testing methods on the erlang module, test
proxies for them on ?MODULE so it's easy to replace
them with buggy versions and see if the bugs are found.

Also the error messages have been improved, comparing
what happened to what was meant to happen.
This makes it a bit more challenging for PropEr to find bugs
since it has less information to go on, so it makes for a
slightly more interesting example.

The change made it necessary to change the precondition for
get/1 to always return true since we need to be able to
get keys that should be undefined to detect if the erase
function is no longer working.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant