From: Andre Nathan <andre@digirati.com.br>
To: caml-list@inria.fr
Subject: [ANN] OSpec 0.1.0 - BDD for OCaml
Date: Thu, 02 Apr 2009 23:52:46 -0300 [thread overview]
Message-ID: <1238727166.6004.12.camel@homesick> (raw)
Hello
I'm happy to announce the first public release of OSpec, an RSpec-inspired
Behavior-Driven Development library for OCaml using a Camlp4 syntax
extension. You can download this release from the ocamlcore forge at
http://forge.ocamlcore.org/projects/ospec/
or directly clone the repository from Github:
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
OSpec also supports before/after blocks, helper functions to aid in
specification writing, two different report formats and an extension
to the "match" syntax so tha you can use it in your expectations.
Please refer to the README file for details.
Best regards,
Andre
reply other threads:[~2009-04-03 2:48 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=1238727166.6004.12.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