Rails%203%20In%20Action

156 CHAPTER 7 Basic access control
expected #has_content?("newadmin@ticketee.com (Admin)")
to return true, got false
This failure occurs because admin isn’t a mass-assignable attribute and therefore isn’t
set and because the user’s admin status isn’t displayed anywhere on the page. One
thing at a time. First, change the create action in Admin::UsersController to set the
admin field before you attempt to save the user, as shown in the following listing.
Listing 7.25 app/controllers/admin/users_controller.rb
...
@user = User.new(params[:user])
@user.admin = params[:user][:admin] == "1"
if @user.save
...
This code sets the admin attribute on the user, which is one of the two things you need
to get this step to pass. The second problem is that only the user’s email address is displayed:
no text appears to indicate they’re a user. To get this text to appear, change
the line in app/views/admin/users/index.html.erb from this
to this:
By not calling any methods on the user object and attempting to write it out of the
view, you cause Ruby to call to_s on this method. By default, this outputs something
similar to the following, which isn’t human friendly:
#
You can override the to_s method on the User model to provide the string containing
the email and admin status of the user by putting the following code inside the class
definition in app/models/user.rb, underneath the attr_accessible line:
def to_s
"#{email} (#{admin? ? "Admin" : "User"})"
end
Now that the admin field is set and displayed on the page, the feature should pass
when you run bin/cucumber features/creating_users.feature:
3 scenarios (3 passed)
33 steps (33 passed)
This is another great time to commit, and again, run rake cucumber:ok spec to make
sure everything works:
28 scenarios (28 passed)
288 steps (288 passed)
# and
14 examples, 0 failures, 7 pending