diff options
author | eregon <eregon@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-12-30 00:05:56 +0000 |
---|---|---|
committer | eregon <eregon@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-12-30 00:05:56 +0000 |
commit | 7f54f1b5543b4a3267a64c47cff9127cbcafcc42 (patch) | |
tree | b4321a0e6aca9aed1a05cfc97b9ca209a5e5a0fd /spec/ruby/README.md | |
parent | 2eee74ef54a2e23eb870680a83dcf74c5d9d9d01 (diff) |
Update to ruby/spec@2d89e48
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66645 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'spec/ruby/README.md')
-rw-r--r-- | spec/ruby/README.md | 20 |
1 files changed, 15 insertions, 5 deletions
diff --git a/spec/ruby/README.md b/spec/ruby/README.md index eef4e9ca0b..eb652bafa8 100644 --- a/spec/ruby/README.md +++ b/spec/ruby/README.md @@ -28,12 +28,22 @@ ruby/spec is known to be tested in these implementations for every commit: * [TruffleRuby](https://github.com/oracle/truffleruby/tree/master/spec/ruby) * [Opal](https://github.com/opal/opal/tree/master/spec) +ruby/spec describes the behavior of Ruby 2.3 and more recent Ruby versions. +More precisely, every latest stable MRI release should [pass](https://travis-ci.org/ruby/spec) all specs of ruby/spec (2.3.x, 2.4.x, 2.5.x, 2.6.x, etc), and those are tested in TravisCI. + The specs are synchronized both ways around once a month by @eregon between ruby/spec, MRI, JRuby and TruffleRuby. -Each of these repositories has a full copy of the files to ease editing specs. +Each of these repositories has a full copy of the specs under `spec/ruby` to ease editing specs. +Any of these repositories can be used to add or edit specs, use what is most convenient for you. -ruby/spec describes the behavior of Ruby 2.3 and more recent Ruby versions. -More precisely, every latest stable MRI release [passes](https://rubyci.org/) all specs of ruby/spec -(2.3.x, 2.4.x, 2.5.x, etc). +For *testing* a Ruby implementation, one should always test against the implementation's copy of the specs under `spec/ruby`, as that's what the Ruby implementation tests against in their CI. +Also, this repository doesn't always contain the latest spec changes from MRI (it's synchronized monthly), and does not contain tags (specs marked as failing on that Ruby implementation). +Running specs in a Ruby implementation can be done with: + +``` +$ cd ruby_implementation/spec/ruby +# Add ../ruby_implementation/bin in PATH, or pass -t /path/to/bin/ruby +$ ../mspec/bin/mspec +``` For older specs try these commits: * Ruby 2.0.0-p647 - [Suite](https://github.com/ruby/spec/commit/245862558761d5abc676843ef74f86c9bcc8ea8d) using [MSpec](https://github.com/ruby/mspec/commit/f90efa068791064f955de7a843e96e2d7d3041c2) (may encounter 2 failures) @@ -63,7 +73,7 @@ This will execute all the specs using the executable named `ruby` on your curren ### Running Specs with a Specific Ruby Implementation Use the `-t` option to specify the Ruby implementation with which to run the specs. -The argument may be a full path to the Ruby binary. +The argument is either a full path to the Ruby binary, or an executable in `$PATH`. $ ../mspec/bin/mspec -t /path/to/some/bin/ruby |