public
Description: Is *your* coverage this sexy?
Clone URL: git://github.com/elliottcable/lingerie.git
elliottcable (author)
Wed Apr 16 03:35:31 -0700 2008
commit  0e1476503a3d8c47e10336ec6a7de441e7e2d812
tree    86d8c1348acc8c5c190bfc3283cb6b1145755b79
name age message
file README.mkdn Wed Apr 16 03:35:31 -0700 2008 Mmmm, let's get comfortable, honey (-;< [elliottcable]
directory bugs/ Wed Apr 16 03:35:31 -0700 2008 Mmmm, let's get comfortable, honey (-;< [elliottcable]
README.mkdn

Lingerie

Lingerie is... sexy coverage. No, really.

Philosophy & goals

The idea is still nebulous (invoked by a conversation about how sexy RDie's coverage was, when we hit 100%), but I hope to end up with an easy to use and unobtrusive system to integrate, track, and manage development in Ruby. It's purpose is to help keep your meta-coding practices such as testing, speccing, and planning all in line. Specifically, I hope to integrate and interface with RSpec, RCov, Git, Ditz, and possibly other useful meta-developmental tools.

Getting

The authoritative source for this project is available at http://github.com/elliottcable/lingerie. You can clone your own copy with the following command:

git clone git://github.com/elliottcable/lingerie.git

If you want to make changes to the codebase, you need to fork your own github repository for said changes. Send a pullrequest to elliottcable when you've got something ready for the master that you think should be integrated into the root source.

Bugs or feature requests can be submitted by forking a repository as previously described, and then using Ditz to add an issue.

Requirements

To run fora, you need the following gems:

  • unknown as of yet

To develop and contribute to fora, you also need:

  • rspec
  • rake
  • rcov
  • ditz