ENV stubbing via a shared context for more powerful tests. Installation Add this line to your application’s Gemfile: gem 'rspec-stubbed_env', group: :test And then execute: $ bundle Or install it yourself as: $ gem install rspec-stubbed_env You must configure RSpec to use the :expect syntax, or some compatible alternative. RSpec.configure do |config| config.expect_with :rspec do |c| c.
Allows you to use block_is_expected similarly to how you would use is_expected if a block was wrapping the subject. This gem does one very simple thing very well. It allows you to use block_is_expected similarly to how you would use is_expected if a block was wrapping the subject. Supports the same versions of Ruby that RSpec does, 1.
Mark specs pending or skipped for specific Ruby engine (e.g. MRI or JRuby) / version combinations. Easiest to just show you: it("blah is blah") do pending_for(engine: "rbx") pending_for(engine: "ruby", versions: "2.1.5") pending_for(engine: "jruby", versions: "2.2.2", reason: "due to a bug in Ruby") pending_for(engine: "ruby", versions: "2.0.0", reason: "because I don't have the time") expect("blah").to eq "blah" end Installation Add this line to your application’s Gemfile:
An Email Condom for your Ruby Server sanitize_email This gem allows you to override your mail delivery settings, globally or in a local context. It is like a Ruby encrusted condom for your email server, just in case it decides to have intercourse with other servers via sundry mail protocols. Summary It’s particularly helpful when you want to prevent the delivery of email (e.