foretspaisibles / broken Goto Github PK

The number one deficiency I find in all OCaml unit testing frameworks today is the lack of integration with Async/Lwt. To me this means two things:

1. Having tests that return a Lwt.t (or a Deferred.t)

2. Test runner that is aware of the lwt/async scheduler

Would you recommend to use broken to test Lwt code? If so, how should one do it?

For each project using Broken it should be possible to keep track of the results of tests run.

Each test case run should store and identifier for the source tree, a timestamp and its outcome.

Here's the error that I get:

ERROR while installing broken.0.4.2 ======================================#
# opam-version 1.2.2
# os           linux
# command      /usr/bin/bmake -I/home/rgrinberg/.opam/pgd/share/bsdowl install
# path         /home/rgrinberg/.opam/pgd/build/broken.0.4.2
# compiler     4.02.3
# exit-code    1
# env-file     /home/rgrinberg/.opam/pgd/build/broken.0.4.2/broken-7696-6d07ae.env
# stdout-file  /home/rgrinberg/.opam/pgd/build/broken.0.4.2/broken-7696-6d07ae.out
# stderr-file  /home/rgrinberg/.opam/pgd/build/broken.0.4.2/broken-7696-6d07ae.err
### stdout ###
# [...]
# /usr/bin/install -c -d -o rgrinberg -g users /home/rgrinberg/.opam/pgd/share/doc/broken/html
# (cd broken_html && sh -c '(find $1 -depth $3 | cpio -dump $2 >/dev/null 2>&1) && find $1 -depth $3 -type d -exec chmod 755 $2/{} \; && find $1 -depth $3 -type f -exec chmod 440 $2/{} \;' COPYTREE_DOC . /home/rgrinberg/.opam/pgd/share/doc/broken/html)
# *** Error code 127
#
# Stop.
# bmake[1]: stopped in /home/rgrinberg/.opam/pgd/build/broken.0.4.2/manual
# *** Error code 1
#
# Stop.
# bmake: stopped in /home/rgrinberg/.opam/pgd/build/broken.0.4.2

I'm wondering why are the docs being built at all however? It's customary to only build docs in the optional build-doc: setting in the opam file.

I guess cpio should be added to depexts?

— Armaël

The interface of the Broken has to be simplified, especially what testsuites are, how they are created and how they are run.

As a Travis CI user, I need to see all details about failed cases on standard output, which imply I need tools:

• To print the number of failed cases and various other figures, such as histograms and so on.
• To print the messages left by failed tests.

The assert_command predicate runs a command and tests for its return code and output.