Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8060337
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 5, 20262026-06-05T09:57:18+00:00 2026-06-05T09:57:18+00:00

I setup Devise so I can write controller specs with this . Then I

  • 0

I setup Devise so I can write controller specs with this.
Then I setup Devise so users cannot delete their accounts.

Now I want to write a spec to make sure the controller is unable to call the destroy action on the Devise user. How do I write this?

In my controller the Devise part looks like this

devise_for :users, skip: :registrations do
  resource :registration,
    only: [:new, :create, :edit, :update],
    path: 'users',
    path_names: { new: 'sign_up' },
    controller: 'devise/registrations',
    as: :user_registration do
    get :cancel
  end
end

In my spec I’m trying to do the following but it doesn’t work. I’m not even sure I’m writing it right. I think the page I’m trying to access is wrong.

describe UsersController do
  login_user # from devise controller helper

  it "does not allow deleting of user" do
    get :users, :method => :delete

    # assert here user was not deleted
  end
end
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-05T09:57:20+00:00Added an answer on June 5, 2026 at 9:57 am

    I think what you really want to test is whether or not the route exists for the registrations#destroy action. If there is no route, then the action will not be called since it can’t be routed to the controller.

    For a destroy action, we need to try to route a DELETE action to the users path. so, something like this might do the trick:

    { :delete=> "/users" }.should_not be_routable
    

    Test syntax pulled from a similar answer here:
    Rails RSpec Routing: Testing actions in :except do NOT route

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Alright I have two roles setup in Devise: User and Employer. Right now you
I'm trying to setup a profiles controller to work with devise registered members. I've
To sum it up, I need to do this: 12345(hWnd) -> C:\setup.exe Right now,
Can anyone help me get to the bottom of this problem? I'm using Devise
I'm trying to setup a bluetooth server for one device with Qt and can't
I have a Rails 3.2 app setup with Devise. Everything works great except for
I setup Facebook login with Devise and omniauth with these instructions https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview The Devise
Assume a device has never seen another device before, in this setup it will
is there a full setup guide for mongo_mapper, haml, rails3 and devise, for the
Application-Stack: Rails3, CanCan, Devise, Shoulda I've got some nested Resources and want to test

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.