Browse files

Move paragraph about EUnit issue capturing stdout to Common problems

  • Loading branch information...
1 parent 44bddfb commit 75c990db62a976561169ffda24b0936d5ba265b2 @kostis kostis committed Oct 18, 2012
Showing with 11 additions and 11 deletions.
  1. +11 −11
@@ -107,18 +107,9 @@ Quickstart guide
-A note about running PropEr from EUnit
+ See also the section common problems below if you want to run
+ PropEr from EUnit.
-[EUnit captures standard output][eunit stdout], so normally PropEr output is
-not visible when `proper:quickcheck()` is invoked from EUnit. You can work
-around this by passing an `{to_file, user}` to `proper:quickcheck/2`. For
- ?assertEqual(true,
- proper:quickcheck(your_module:some_property(), [{to_file, user}]).
-This will make PropEr properties visible also when invoked from EUnit.
Where to go from here
@@ -139,6 +130,15 @@ The main issue is that both systems define a `?LET` macro. To avoid a potential
clash, simply include PropEr's header file before EUnit's. That way, any
instance of `?LET` will count as a PropEr `?LET`.
+Another issue is that [EUnit captures standard output][eunit stdout],
+so normally PropEr output is not visible when `proper:quickcheck()` is
+invoked from EUnit. You can work around this by passing the option
+`{to_file, user}` to `proper:quickcheck/2`. For example:
+ ?assertEqual(true, proper:quickcheck(your_mod:some_prop(), [{to_file,user}]).
+This will make PropEr properties visible also when invoked from EUnit.
Incompatibilities with QuviQ's QuickCheck

0 comments on commit 75c990d

Please sign in to comment.