From: Andre Nathan <andre@digirati.com.br>
To: caml-list@inria.fr
Subject: [ANN] OSpec - BDD for OCaml
Date: Wed, 25 Mar 2009 18:18:12 -0300 [thread overview]
Message-ID: <1238015892.5992.20.camel@homesick> (raw)
Hello
I would like to announce the availability of OSpec, an RSpec-inspired
Behavior-Driven Development library for OCaml using a Camlp4 syntax
extension. It is available at
http://github.com/andrenth/ospec/tree/master
Here's a simple example of OSpec's syntax:
describe "An even number" do
it "should be divisible by two" do
let divisible_by_two x = x mod 2 = 0 in
42 should be divisible_by_two
done;
(* or simply: *)
it "should be divisible by two" do
(42 mod 2) should = 0
done
done
I must say that this is the first time I use Camlp4 (in fact I started
writing this to learn about it), so there are probably better ways to
accomplish the functionality that OSpec provides. The code is horrible
and it will make your eyes bleed. However, since there was a question
about the availability of such a library recently on the list, I decided
to make it public. Maybe I can get some contributions to this :)
Best regards,
Andre
reply other threads:[~2009-03-25 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1238015892.5992.20.camel@homesick \
--to=andre@digirati.com.br \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).