You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PropEr's quick-start instructions in the project README do not:
detail integrating with rebar or old-style project makefile,
show running a property test suite as opposed to single property tests in the erlang shell, by hand and
link to resources that address the above (I note the website's User Guide is the project README and the Tutorials do not clearly address this, either).
Detail integrating with rebar or old-style project makefile
To the first point, I note that rebar's ta-qc branch which provides support for PropEr hasn't seen any action in a year. It seems reasonable to me that PropEr should:
provide a utility to run proper tests without relying on an external build tool.
Setting up paths appropriately and finding the property tests to run is somewhat involved but is doable without recourse to rebar. I note that Haskell's QuickCheck supports no discovery of tests, but providing out-of-the-box running for tests placed in a well-known area is increasingly a feature of modern test tools.
Show running a property test suite as opposed to single property tests in the erlang shell, by hand.
The resolution of this sub-problem is highly dependent on the resolution of the above. Most pragmatic to the PropEr project is probably piggy-backing on eunit, but that is annoyingly verbose and of poor work saving utility to subsequent developers.
Link to resources that address the above
An example project--not necessarily complex--would do wonders.
The text was updated successfully, but these errors were encountered:
PropEr's quick-start instructions in the project README do not:
Detail integrating with rebar or old-style project makefile
To the first point, I note that rebar's
ta-qc
branch which provides support for PropEr hasn't seen any action in a year. It seems reasonable to me that PropEr should:Setting up paths appropriately and finding the property tests to run is somewhat involved but is doable without recourse to rebar. I note that Haskell's QuickCheck supports no discovery of tests, but providing out-of-the-box running for tests placed in a well-known area is increasingly a feature of modern test tools.
Show running a property test suite as opposed to single property tests in the erlang shell, by hand.
The resolution of this sub-problem is highly dependent on the resolution of the above. Most pragmatic to the PropEr project is probably piggy-backing on eunit, but that is annoyingly verbose and of poor work saving utility to subsequent developers.
Link to resources that address the above
An example project--not necessarily complex--would do wonders.
The text was updated successfully, but these errors were encountered: