bmabey / rspec-dev forked from dchelimsky/rspec-dev

Resources for rspec developers/contributors

This URL has Read+Write access

commit  4b36ba05639f7a587321f16f9f617953cfd6dd7d
tree    da0b682b31a0eec4859cc9b77d3c504079d537b0
parent  27ea36f78efeb2ddb9aa8f8eac18b8170dac2687
rspec-dev / README
100644 41 lines (30 sloc) 1.497 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
=== This project is for RSpec developers/contributors.
 
== Getting the entire development tree:
 
  git-clone git://github.com/dchelimsky/rspec-dev.git
  cd rspec-dev
  rake git:update
 
== Running RSpec's specs
 
In order to run RSpec's full suite of specs (rake pre_commit) you must install the following gems:
 
* rake # Runs the build script
* rcov # Verifies that the code is 100% covered by specs
* webby # Generates the static HTML website
* syntax # Required to highlight ruby code
* diff-lcs # Required if you use the --diff switch
* win32console # Required by the --colour switch if you're on Windows
* meta_project # Required in order to make releases at RubyForge
* heckle # Required if you use the --heckle switch
* hpricot # Used for parsing HTML from the HTML output formatter in RSpec's own specs
 
Once those are all installed, you should be able to run the suite with the following steps:
 
* cd rspec-dev
* rake install_dependencies
* cd example_rails_app
* export RSPEC_RAILS_VERSION=2.0.2
* rake rspec:generate_sqlite3_config
* cd ..
* rake pre_commit
 
Note that RSpec itself - once built - doesn't have any dependencies outside the Ruby core
and stdlib - with a few exceptions:
 
* The spec command line uses diff-lcs when --diff is specified.
* The spec command line uses heckle when --heckle is specified.
* The Spec::Rake::SpecTask needs RCov if RCov is enabled in the task.
 
See http://rspec.info for further documentation.