Testing create Action using RSpec in Rails











up vote
0
down vote

favorite












I am using RSpec to test my controller actions and have been successfully tested my index, show, edit actions so far. But for create action it is giving me the following error for valid attributes. I'm using rails 5 and ruby 2.5.3. Can't understand what am I doing wrong.



file /spec/factories/leaves.rb



FactoryBot.define do
factory :leave do
id {Faker::Number.between(from = 1, to = 3)}
user_id {Faker::Number.between(from = 1, to = 3)}
team_lead_id {Faker::Number.between(from = 1, to = 3)}
fiscal_year_id {Faker::Number.between(from = 1, to = 3)}
start_day {Date.today - Faker::Number.number(3).to_i.days}
end_day {Date.today - Faker::Number.number(3).to_i.days}
reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
status {Faker::Number.between(from = 1, to = 3)}

factory :invalid_leave do
user_id nil
end
end
end


file /spec/controllers/leave_controller_spec.rb



context 'with valid attributes' do
it 'saves the new leave in the database' do
leave_params = FactoryBot.attributes_for(:leave)
expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
end
it 'redirects to leave#index' do
render_template :index
end
end


file /app/controller/leave_controller.rb



def create
@leave = Leave.new(leave_params)

if @leave.save
flash[:notice] = t('leave.leave_create')
redirect_to leave_index_path
else
flash[:notice] = t('leave.leave_create_error')
redirect_to leave_index_path
end

end


The error is:



LeaveController POST#create with valid attributes saves the new leave in the database
Failure/Error: expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
expected `Leave.count` to have changed by 1, but was changed by 0
# ./spec/controllers/leave_controller_spec.rb:64:in `block (4 levels) in <top (required)>'


Update Leave Database



create_table "leaves", force: :cascade do |t|
t.integer "user_id", null: false
t.integer "team_lead_id", null: false
t.integer "fiscal_year_id", null: false
t.date "start_day", null: false
t.date "end_day", null: false
t.text "reason", null: false
t.integer "status", null: false
t.string "comment"
t.datetime "created_at", null: false
t.datetime "updated_at", null: false
end


Leave Model



class Leave < ApplicationRecord
validates :user_id, :team_lead_id, :fiscal_year_id, :start_day, :end_day, :reason, :status, presence: true
end









share|improve this question
























  • can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
    – richflow
    Nov 22 at 8:10















up vote
0
down vote

favorite












I am using RSpec to test my controller actions and have been successfully tested my index, show, edit actions so far. But for create action it is giving me the following error for valid attributes. I'm using rails 5 and ruby 2.5.3. Can't understand what am I doing wrong.



file /spec/factories/leaves.rb



FactoryBot.define do
factory :leave do
id {Faker::Number.between(from = 1, to = 3)}
user_id {Faker::Number.between(from = 1, to = 3)}
team_lead_id {Faker::Number.between(from = 1, to = 3)}
fiscal_year_id {Faker::Number.between(from = 1, to = 3)}
start_day {Date.today - Faker::Number.number(3).to_i.days}
end_day {Date.today - Faker::Number.number(3).to_i.days}
reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
status {Faker::Number.between(from = 1, to = 3)}

factory :invalid_leave do
user_id nil
end
end
end


file /spec/controllers/leave_controller_spec.rb



context 'with valid attributes' do
it 'saves the new leave in the database' do
leave_params = FactoryBot.attributes_for(:leave)
expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
end
it 'redirects to leave#index' do
render_template :index
end
end


file /app/controller/leave_controller.rb



def create
@leave = Leave.new(leave_params)

if @leave.save
flash[:notice] = t('leave.leave_create')
redirect_to leave_index_path
else
flash[:notice] = t('leave.leave_create_error')
redirect_to leave_index_path
end

end


The error is:



LeaveController POST#create with valid attributes saves the new leave in the database
Failure/Error: expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
expected `Leave.count` to have changed by 1, but was changed by 0
# ./spec/controllers/leave_controller_spec.rb:64:in `block (4 levels) in <top (required)>'


Update Leave Database



create_table "leaves", force: :cascade do |t|
t.integer "user_id", null: false
t.integer "team_lead_id", null: false
t.integer "fiscal_year_id", null: false
t.date "start_day", null: false
t.date "end_day", null: false
t.text "reason", null: false
t.integer "status", null: false
t.string "comment"
t.datetime "created_at", null: false
t.datetime "updated_at", null: false
end


Leave Model



class Leave < ApplicationRecord
validates :user_id, :team_lead_id, :fiscal_year_id, :start_day, :end_day, :reason, :status, presence: true
end









share|improve this question
























  • can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
    – richflow
    Nov 22 at 8:10













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am using RSpec to test my controller actions and have been successfully tested my index, show, edit actions so far. But for create action it is giving me the following error for valid attributes. I'm using rails 5 and ruby 2.5.3. Can't understand what am I doing wrong.



file /spec/factories/leaves.rb



FactoryBot.define do
factory :leave do
id {Faker::Number.between(from = 1, to = 3)}
user_id {Faker::Number.between(from = 1, to = 3)}
team_lead_id {Faker::Number.between(from = 1, to = 3)}
fiscal_year_id {Faker::Number.between(from = 1, to = 3)}
start_day {Date.today - Faker::Number.number(3).to_i.days}
end_day {Date.today - Faker::Number.number(3).to_i.days}
reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
status {Faker::Number.between(from = 1, to = 3)}

factory :invalid_leave do
user_id nil
end
end
end


file /spec/controllers/leave_controller_spec.rb



context 'with valid attributes' do
it 'saves the new leave in the database' do
leave_params = FactoryBot.attributes_for(:leave)
expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
end
it 'redirects to leave#index' do
render_template :index
end
end


file /app/controller/leave_controller.rb



def create
@leave = Leave.new(leave_params)

if @leave.save
flash[:notice] = t('leave.leave_create')
redirect_to leave_index_path
else
flash[:notice] = t('leave.leave_create_error')
redirect_to leave_index_path
end

end


The error is:



LeaveController POST#create with valid attributes saves the new leave in the database
Failure/Error: expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
expected `Leave.count` to have changed by 1, but was changed by 0
# ./spec/controllers/leave_controller_spec.rb:64:in `block (4 levels) in <top (required)>'


Update Leave Database



create_table "leaves", force: :cascade do |t|
t.integer "user_id", null: false
t.integer "team_lead_id", null: false
t.integer "fiscal_year_id", null: false
t.date "start_day", null: false
t.date "end_day", null: false
t.text "reason", null: false
t.integer "status", null: false
t.string "comment"
t.datetime "created_at", null: false
t.datetime "updated_at", null: false
end


Leave Model



class Leave < ApplicationRecord
validates :user_id, :team_lead_id, :fiscal_year_id, :start_day, :end_day, :reason, :status, presence: true
end









share|improve this question















I am using RSpec to test my controller actions and have been successfully tested my index, show, edit actions so far. But for create action it is giving me the following error for valid attributes. I'm using rails 5 and ruby 2.5.3. Can't understand what am I doing wrong.



file /spec/factories/leaves.rb



FactoryBot.define do
factory :leave do
id {Faker::Number.between(from = 1, to = 3)}
user_id {Faker::Number.between(from = 1, to = 3)}
team_lead_id {Faker::Number.between(from = 1, to = 3)}
fiscal_year_id {Faker::Number.between(from = 1, to = 3)}
start_day {Date.today - Faker::Number.number(3).to_i.days}
end_day {Date.today - Faker::Number.number(3).to_i.days}
reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
status {Faker::Number.between(from = 1, to = 3)}

factory :invalid_leave do
user_id nil
end
end
end


file /spec/controllers/leave_controller_spec.rb



context 'with valid attributes' do
it 'saves the new leave in the database' do
leave_params = FactoryBot.attributes_for(:leave)
expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
end
it 'redirects to leave#index' do
render_template :index
end
end


file /app/controller/leave_controller.rb



def create
@leave = Leave.new(leave_params)

if @leave.save
flash[:notice] = t('leave.leave_create')
redirect_to leave_index_path
else
flash[:notice] = t('leave.leave_create_error')
redirect_to leave_index_path
end

end


The error is:



LeaveController POST#create with valid attributes saves the new leave in the database
Failure/Error: expect{ post :create, params: {leave: leave_params}}.to change(Leave,:count).by(1)
expected `Leave.count` to have changed by 1, but was changed by 0
# ./spec/controllers/leave_controller_spec.rb:64:in `block (4 levels) in <top (required)>'


Update Leave Database



create_table "leaves", force: :cascade do |t|
t.integer "user_id", null: false
t.integer "team_lead_id", null: false
t.integer "fiscal_year_id", null: false
t.date "start_day", null: false
t.date "end_day", null: false
t.text "reason", null: false
t.integer "status", null: false
t.string "comment"
t.datetime "created_at", null: false
t.datetime "updated_at", null: false
end


Leave Model



class Leave < ApplicationRecord
validates :user_id, :team_lead_id, :fiscal_year_id, :start_day, :end_day, :reason, :status, presence: true
end






ruby-on-rails ruby rspec






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 9:42

























asked Nov 22 at 7:00









user5756014

11310




11310












  • can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
    – richflow
    Nov 22 at 8:10


















  • can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
    – richflow
    Nov 22 at 8:10
















can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
– richflow
Nov 22 at 8:10




can you post your schema for Leave? you could also change your create action to call @leave.save! and see if it raises any errors when trying to save.
– richflow
Nov 22 at 8:10












2 Answers
2






active

oldest

votes

















up vote
0
down vote













I think that might be because of id which you set in factory. You shouldn't set id attribute in factory. That's why number of Leave objects didn't change.



Additionally, I assume that you have some relations there - user_id, team_lead_id etc. If these relations are necessarry to create leave object then you have to create factories for these models, too.



In the end your factory should look like this



FactoryBot.define do
factory :leave do
user
team_lead
fiscal_year
start_day {Date.today - Faker::Number.number(3).to_i.days}
end_day {Date.today - Faker::Number.number(3).to_i.days}
reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
status {Faker::Number.between(from = 1, to = 3)}

factory :invalid_leave do
user nil
end
end
end


Reference: Factory Bot documentation - associations






share|improve this answer





















  • There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
    – user5756014
    Nov 22 at 7:59










  • I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
    – mefe
    Nov 22 at 9:10










  • Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
    – user5756014
    Nov 22 at 9:44


















up vote
0
down vote



accepted










[For Future Reader] I got it to work by doing the fooling in leave_controller_spec.rb file.



 describe 'POST#create' do

context 'with valid attributes' do
let(:valid_attribute) do
attributes_for(:leave,
user_id: 2,
team_lead_id: 3,
fiscal_year_id: 2,
start_day: '2018-10-10'.to_date,
end_day: '2018-10-10'.to_date,
reason: 'Sick',
status: 2)
end

it 'saves the new leave in the database' do

expect do
post :create, params: {leave: valid_attribute}
end.to change(Leave,:count).by(1)
end
it 'redirects to leave#index' do
render_template :index
end
end





share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425436%2ftesting-create-action-using-rspec-in-rails%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    I think that might be because of id which you set in factory. You shouldn't set id attribute in factory. That's why number of Leave objects didn't change.



    Additionally, I assume that you have some relations there - user_id, team_lead_id etc. If these relations are necessarry to create leave object then you have to create factories for these models, too.



    In the end your factory should look like this



    FactoryBot.define do
    factory :leave do
    user
    team_lead
    fiscal_year
    start_day {Date.today - Faker::Number.number(3).to_i.days}
    end_day {Date.today - Faker::Number.number(3).to_i.days}
    reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
    status {Faker::Number.between(from = 1, to = 3)}

    factory :invalid_leave do
    user nil
    end
    end
    end


    Reference: Factory Bot documentation - associations






    share|improve this answer





















    • There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
      – user5756014
      Nov 22 at 7:59










    • I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
      – mefe
      Nov 22 at 9:10










    • Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
      – user5756014
      Nov 22 at 9:44















    up vote
    0
    down vote













    I think that might be because of id which you set in factory. You shouldn't set id attribute in factory. That's why number of Leave objects didn't change.



    Additionally, I assume that you have some relations there - user_id, team_lead_id etc. If these relations are necessarry to create leave object then you have to create factories for these models, too.



    In the end your factory should look like this



    FactoryBot.define do
    factory :leave do
    user
    team_lead
    fiscal_year
    start_day {Date.today - Faker::Number.number(3).to_i.days}
    end_day {Date.today - Faker::Number.number(3).to_i.days}
    reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
    status {Faker::Number.between(from = 1, to = 3)}

    factory :invalid_leave do
    user nil
    end
    end
    end


    Reference: Factory Bot documentation - associations






    share|improve this answer





















    • There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
      – user5756014
      Nov 22 at 7:59










    • I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
      – mefe
      Nov 22 at 9:10










    • Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
      – user5756014
      Nov 22 at 9:44













    up vote
    0
    down vote










    up vote
    0
    down vote









    I think that might be because of id which you set in factory. You shouldn't set id attribute in factory. That's why number of Leave objects didn't change.



    Additionally, I assume that you have some relations there - user_id, team_lead_id etc. If these relations are necessarry to create leave object then you have to create factories for these models, too.



    In the end your factory should look like this



    FactoryBot.define do
    factory :leave do
    user
    team_lead
    fiscal_year
    start_day {Date.today - Faker::Number.number(3).to_i.days}
    end_day {Date.today - Faker::Number.number(3).to_i.days}
    reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
    status {Faker::Number.between(from = 1, to = 3)}

    factory :invalid_leave do
    user nil
    end
    end
    end


    Reference: Factory Bot documentation - associations






    share|improve this answer












    I think that might be because of id which you set in factory. You shouldn't set id attribute in factory. That's why number of Leave objects didn't change.



    Additionally, I assume that you have some relations there - user_id, team_lead_id etc. If these relations are necessarry to create leave object then you have to create factories for these models, too.



    In the end your factory should look like this



    FactoryBot.define do
    factory :leave do
    user
    team_lead
    fiscal_year
    start_day {Date.today - Faker::Number.number(3).to_i.days}
    end_day {Date.today - Faker::Number.number(3).to_i.days}
    reason {Faker::Lorem.sentences(sentence_count = 3, supplemental = false)}
    status {Faker::Number.between(from = 1, to = 3)}

    factory :invalid_leave do
    user nil
    end
    end
    end


    Reference: Factory Bot documentation - associations







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 22 at 7:47









    mefe

    771213




    771213












    • There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
      – user5756014
      Nov 22 at 7:59










    • I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
      – mefe
      Nov 22 at 9:10










    • Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
      – user5756014
      Nov 22 at 9:44


















    • There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
      – user5756014
      Nov 22 at 7:59










    • I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
      – mefe
      Nov 22 at 9:10










    • Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
      – user5756014
      Nov 22 at 9:44
















    There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
    – user5756014
    Nov 22 at 7:59




    There is no relation between them right now. Just wanted to see if I can run RSpec for post request of a CRUD operation. Thus this advice isn't applicable here. Thank you though.
    – user5756014
    Nov 22 at 7:59












    I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
    – mefe
    Nov 22 at 9:10




    I see. It would be useful if you post Leave model definition, too. Anyway - have you tried removing id attribute from factory?
    – mefe
    Nov 22 at 9:10












    Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
    – user5756014
    Nov 22 at 9:44




    Hi, I added the Leave database and model. Also tried removing "id" from factory, but no go.
    – user5756014
    Nov 22 at 9:44












    up vote
    0
    down vote



    accepted










    [For Future Reader] I got it to work by doing the fooling in leave_controller_spec.rb file.



     describe 'POST#create' do

    context 'with valid attributes' do
    let(:valid_attribute) do
    attributes_for(:leave,
    user_id: 2,
    team_lead_id: 3,
    fiscal_year_id: 2,
    start_day: '2018-10-10'.to_date,
    end_day: '2018-10-10'.to_date,
    reason: 'Sick',
    status: 2)
    end

    it 'saves the new leave in the database' do

    expect do
    post :create, params: {leave: valid_attribute}
    end.to change(Leave,:count).by(1)
    end
    it 'redirects to leave#index' do
    render_template :index
    end
    end





    share|improve this answer

























      up vote
      0
      down vote



      accepted










      [For Future Reader] I got it to work by doing the fooling in leave_controller_spec.rb file.



       describe 'POST#create' do

      context 'with valid attributes' do
      let(:valid_attribute) do
      attributes_for(:leave,
      user_id: 2,
      team_lead_id: 3,
      fiscal_year_id: 2,
      start_day: '2018-10-10'.to_date,
      end_day: '2018-10-10'.to_date,
      reason: 'Sick',
      status: 2)
      end

      it 'saves the new leave in the database' do

      expect do
      post :create, params: {leave: valid_attribute}
      end.to change(Leave,:count).by(1)
      end
      it 'redirects to leave#index' do
      render_template :index
      end
      end





      share|improve this answer























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        [For Future Reader] I got it to work by doing the fooling in leave_controller_spec.rb file.



         describe 'POST#create' do

        context 'with valid attributes' do
        let(:valid_attribute) do
        attributes_for(:leave,
        user_id: 2,
        team_lead_id: 3,
        fiscal_year_id: 2,
        start_day: '2018-10-10'.to_date,
        end_day: '2018-10-10'.to_date,
        reason: 'Sick',
        status: 2)
        end

        it 'saves the new leave in the database' do

        expect do
        post :create, params: {leave: valid_attribute}
        end.to change(Leave,:count).by(1)
        end
        it 'redirects to leave#index' do
        render_template :index
        end
        end





        share|improve this answer












        [For Future Reader] I got it to work by doing the fooling in leave_controller_spec.rb file.



         describe 'POST#create' do

        context 'with valid attributes' do
        let(:valid_attribute) do
        attributes_for(:leave,
        user_id: 2,
        team_lead_id: 3,
        fiscal_year_id: 2,
        start_day: '2018-10-10'.to_date,
        end_day: '2018-10-10'.to_date,
        reason: 'Sick',
        status: 2)
        end

        it 'saves the new leave in the database' do

        expect do
        post :create, params: {leave: valid_attribute}
        end.to change(Leave,:count).by(1)
        end
        it 'redirects to leave#index' do
        render_template :index
        end
        end






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 22 at 11:50









        user5756014

        11310




        11310






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425436%2ftesting-create-action-using-rspec-in-rails%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            What visual should I use to simply compare current year value vs last year in Power BI desktop

            Alexandru Averescu

            Trompette piccolo