Port of minitest/pride to rspec3
Failed to load latest commit information.
.gitignore Ignore the pkg. directory Jan 14, 2015
LICENSE.txt Update copyright in the LICENSE Apr 5, 2016
README.markdown Update graphics and copyright in the README Apr 5, 2016
Rakefile Merge pending/failure specs Apr 5, 2016
rspec-pride.gemspec Bump version and update the HISTORY file Apr 5, 2016



Take pride in your test output!

Mimics the functionality of minitest/pride for RSpec 3

Prideful Failure Prideful Success

How to use Rspec-pride

To use rspec-pride, you need to call rspec kind of like this:

rspec --require rspec/pride --format PrideFormatter

Or put those options in your .rspec file.


The tests are a lie! They don't test rspec-pride directly, they just produce enough output so that you can visually verify that everything is working. This was much faster than writing actual tests and works just as well in this case.

Contributing to Rspec-pride

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.


Copyright (c) 2011-2016 Mark Rada. See LICENSE.txt for further details.

Bitdeli Badge