proper

proper copied to clipboard

Integrate with code coverage?

2

Is there any documentation of showing that the results are integrated with code coverage? For example, would like to see that the tests will add to coder coverage with unit...

linearregression

Question about using proper with Elixir

3

Hi, I would like to use your lib with an Elixir project. Is there a way to integrate it with Elixir or use it with Elixir?

imetallica

Could u add support for the module() type?

2

fredrikelinder

Given the following behaviour ``` erlang -module(bar). -callback behaviour_spec(integer()) -> integer(). ``` and module ``` erlang -module(foo). -behaviour(bar). -export([normal_spec/1, behaviour_spec/1]). -spec normal_spec(integer()) -> integer(). normal_spec(A) -> A + 1. behaviour_spec(A)...

puzza007

run_parallel_commands doesn't handle postcondition result the same way run_commands does

1

run_commands handles exceptions by wrapping them into a postcondition result, while run_parallel_commands (through `check/6`) only checks for true and false.

yrashk

node type supported

2

I needed a proper test for the module that works with the 'node()' type. I'm not sure that it's done correctly as I don't know the code good enough. I've...

gliush

Added unicode generators [PR was resubmitted]

7

Add improper_list/2, maybe_improper_list/2 generators. PR https://github.com/manopapad/proper/pull/62 is an old version of this request.

arcusfelis

why proper not returning error when can't produce enough satisfies instances? I mean in proper:module, proper:check_spec, proper:check_specs... I have just [] ... as result of (proper:check_specs(example): ``` Testing example:size/1 ............................................................................................................................................................................................

andrzejsliwa

Quickstart guide does not mention rebar (or other build tool) and suggests manual running of all property tests.

3

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...

blt

Pretty-printing of shrinked testcase

3

Is there any reason to not represent things like ``` erlang [{init,{state,undefined,{array,0,10,empty,10},208740,large,last}},{set,{var,1},{call,ecirca,new,[208740,last,large]}},{set,{var,4},{call,ecirca,set,[{call,erlang,element,[2,{var,1}]},158910,256964645335393280]}},{set,{var,6},{call,ecirca,slice,[{call,erlang,element,[2,{var,1}]},207505,131476]}}] ``` as ``` erlang A = ecirca:new(208740,last,large), B = ecirca:set(erlang:element(2, A), 158910, 256964645335393280), C = ecirca:slice(erlang:element(2, A), 207505,131476)...

si14