Skip to content

Add the 3.5.0.beta1 release post. #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 53 additions & 0 deletions source/blog/2016-02-06-rspec-3-5-0-beta1-has-been-released.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
title: RSpec 3.5.0.beta1 has been released!
author: Sam Phippen
---

RSpec 3.5.0.beta1 has just been released! This is a big release for us because
it's the first release of RSpec we've published that has anything that could be
described as approximating support for Rails 5.

The purpose of this beta release is to enable people who are upgrading to Rails
5 to check their existing RSpec suites with Rails 5. If you do find any problems
with this release, let us know via GitHub, and we'll hopefully get everything
fixed in time for the Rails 5 release proper.

## Upgrading smoothly

As was discussed at Railsconf this year, Rails "soft deprecated" controller
tests in Rails 5. RSpec has been affected by being downstream of this, but
fortunately, we were able to make the process relatively smooth for our users.

If you have existing specs with `:type => :view` or `:type => :controller`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's slightly confusing that Rails' deprecation of controller tests affect view specs. Not sure if it's worth spending any effort explaining why but I found this surprising.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's because controller specs and view specs use some of the same code paths. Nobody who tests without RSpec uses view tests, so rails isn't really talking about them. The announced deprecations of controller specs also cover view specs.

you'll need to add [the Rails Controller Testing Gem](https://github.com/rails/rails-controller-testing)
to your Gemfile. For the moment we recommend using the version from GitHub, but
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth providing a Gemfile snippet showing how to use the gem from github?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added below.

we hope that there will be a stable version on Rubygems before Rails 5 is released
proper.

Gemfile example:

```ruby
source "https://rubygems.org"

gem "rails-controller-testing", :git => "https://github.com/rails/rails-controller-testing"
gem "rspec-rails", "3.5.0.beta1"
```

## Summing up

Since this is only a beta, I've kept this blog post nice and short. When 3.5.0
final is released we'll do a full post with much more detail. In the mean time,
there are a few people I'd like to say thanks to:

* The entire RSpec core team for their continued work on the project
* [Sean Griffin](https://twitter.com/sgrif), who personally spent a lot of time helping me with fixing up
RSpec's compatability with Rails 5
* [Andrew White](https://twitter.com/pixeltrix), who has also been helping me with RSpec's rails integration in
the past few weeks.
* [Cristiano Betta](https://twitter.com/cbetta) who quickly smoke tested the
release against one of his rails apps for me.

This release was a huge amount of work for everyone involved, and I'm really
glad we're able to get you something to test against Rails 5 ahead of it's
release. We hope you enjoy, and do let us know if you've got any feedback on
this release.