Add property tests for luhn about erlang HOT 7 CLOSED

One argument against this is that it's awfully revealing. Thoughts @maintainers?

from erlang.

I'm very keen on prop-testing, but currently we don't rely on anthing not delivered by OTP.

I do think, that introducing rebar(3) or erlank.mk here just to have some prop testing is too much.

Also this change would not only mean to just PR that single exercise, but also adding necessary stuff into documentation of how to install and get it running. I've touched some tracks where documentation and reality is out of sync drastically and I don't want this to happen to erlang (if possible).

from erlang.

Understandable. Also the tests I wrote have a crude reimplementation of the algorithm, which when shown to users, makes it less fun.

from erlang.

I do think, that property testing will expose at least a partial solution to the problem in general, so even if I am eager to it, I do fear we can't use it.

But since using rebar3 (#106) is a fact that has been decided upon, I will definitively reconsider property testing about next year.

from erlang.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from erlang.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from erlang.

Closing since this is stale and too revealing. The property-based tests I wrote are linked in case anyone is curious in the future.

from erlang.