1
0
Fork 0
mirror of https://github.com/rspec/rspec-metagem.git synced 2022-11-09 12:09:29 -05:00
RSpec meta-gem that depends on the other components
Find a file
Chad Humphries, Nick Ang and Rob Sanheim 8e6a2af13b Fixing rake git:something
Turns out their was a ENV key being set by jeweler that was causing
  the issue.  All fixed now
2009-09-26 20:12:51 -04:00
lib add lib (so you can just require 'rpsec') 2009-06-30 10:22:14 -05:00
.document Initial jeweler repository creation 2009-06-29 12:18:55 -04:00
.gitignore Initial jeweler repository creation 2009-06-29 12:18:55 -04:00
License.txt Initial jeweler repository creation 2009-06-29 12:18:55 -04:00
Rakefile Fixing rake git:something 2009-09-26 20:12:51 -04:00
README.markdown update readme 2009-07-02 09:10:19 -05:00
rspec-meta.gemspec Preparing for 2.0.0a1 release 2009-09-16 11:16:41 -04:00
VERSION Preparing for 2.0.0a1 release 2009-09-16 11:16:41 -04:00
VERSION.yml Preparing for 2.0.0a1 release 2009-09-16 11:16:41 -04:00

RSpec Meta

This is part of the rspec-2 codebase, which is in super-pre-alpha-infancy at the moment. While you are welcome to track, fork, explore, etc, we're too early in the process to start fielding pull requests and or issues from outside the core development team, so please don't waste your time until this notice changes.

This repo will be the source for the rspec-2.x gem, which will serve as a meta-gem, much like the rails and merb gems. gem install rspec will also install rspec-core, rspec-expectations and rspec-mocks, each of which can be installed separately and actived in isolation with the gem command. Among other benefits, this will allow you to use rspec-expectations, for example, in Test::Unit::TestCase if you happen to like that style.

Conversely, if you like RSpec's approach to declaring example groups and examples (describe and it) but prefer Test::Unit assertions and mocha, rr or flexmock for mocking, you'll be able to do that without having to load the components of rspec that you're not using.

Again, we're super early in the process - aiming for a 2.0 release late 2009/early 2010 - so do stay tuned, but don't start using this just yet.

Also see