We love feature requests and bug reports. Here are some guidelines for submitting them.

Tags

Please tag your ticket as either a bug or a featurerequest. If you are submitting a patch (more on patches below), then tag it as patch also.

Titles

We have a lot of tickets here and review them periodically. Please use a meaningful title. Tickets with titles like "example fails" are likely to be ignored, if not rejected.

Patches

We've moved to github. New instructions coming soon ...

Bugs

We want to hear about bugs that you find, but we can’t address them if we can’t reproduce them. If you submit a Bug report, be sure to include:

  • rspec version (either a versioned release or git commit number)
  • rails version (if you’re using the rspec_on_rails plugin)
  • any other relevant versions, OSes, etc
  • a failing example AND code (see sample below) – we need to be able to reproduce the failure. While code snippets are better than nothing, what we really prefer is modifications to RSpec’s own examples, as a unified diff file.
describe "My Problem" do
  it "can be reproduced as follows" do
    # Why doesn't this work?
    # (This is just a silly example)
    true.should be_true
  end
end

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Behaviour Driven Development for Ruby.

Shared Ticket Bins

1.1.595% complete

 

Completed 39 of 41 tickets

Pages