QCheck_ounitval to_ounit_test :
?verbose:bool ->
?long:bool ->
?rand:Random.State.t ->
QCheck.Test.t ->
OUnit.testto_ounit_test ~rand t wraps t into a OUnit test
val to_ounit_test_cell :
?verbose:bool ->
?long:bool ->
?rand:Random.State.t ->
_ QCheck.Test.cell ->
OUnit.testSame as to_ounit_test but with a polymorphic test cell
val (>:::) : string -> QCheck.Test.t list -> OUnit.testSame as OUnit.(>:::) but with a list of QCheck tests
val to_ounit2_test : ?rand:Random.State.t -> QCheck.Test.t -> OUnit2.testto_ounit2_test ?rand t wraps t into a OUnit2 test
val to_ounit2_test_list :
?rand:Random.State.t ->
QCheck.Test.t list ->
OUnit2.test listto_ounit2_test_list ?rand t like to_ounit2_test but for a list of tests
QCheck provides some custom runners for OUnit tests.
Note that OUnit.run_test_tt or OUnit.run_test_tt_main can be used as well, in particular when QCheck tests are mixed with normal unit tests.
For OUnit2 you can use OUnit2.run_test_tt_main.
val run : ?argv:string array -> OUnit.test -> intrun test runs the test, and returns an error code that is 0 if all tests passed, 1 otherwise. This is the default runner used by the comment-to-test generator.
This test runner displays execution in a compact way, making it good for suites that have lots of tests.
Output example:
random seed: 101121210 random seed: 101121210 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Error: tests>error_raise_exn test `error_raise_exn` raised exception `QCheck_ounit_test.Error` on `0 (after 62 shrink steps)` Raised at file "example/QCheck_ounit_test.ml", line 19, characters 20-25 Called from file "src/QCheck.ml", line 846, characters 13-33 /////////////////////////////////////////////////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Failure: tests>fail_sort_id fail_sort_id /////////////////////////////////////////////////////////////////////////////// Ran: 4 tests in: 0.74 seconds. WARNING! SOME TESTS ARE NEITHER SUCCESSES NOR FAILURES!
val run_tap : OUnit.test -> OUnit.test_resultsTAP-compatible test runner, in case we want to use a test harness. It prints one line per test.