ruby - How to request (GET/POST) routes in RSpec that have a wildcard -


i have (admittedly hideous) route in rails:

 scope '/software'   post '/:software_id/:attachment_id/event/*event' => 'software#post_event', as: 'post_event' end

(i change legacy api)

and writing rspec test it.

rake routes gives me:

 post_event post   /software/:software_id/:attachment_id/event/*event(.:format)     api/version1301/software#post_event

my test looks this:

   describe "post_event"      "should respond 204"       params = {         attachment_id: @attachment.uid,         software_id: @license.id       }        post :post_event, params        response.code.should eq "204"     end   end

but following routing error:

 failure/error: post :post_event, params actioncontroller::routingerror: no route matches {:format=>"json", :name_path=>:api, :attachment=>"7b40ab6a-d522-4a86-b0de-dfb8081e4465", :software_id=>"0000001", :attachment_id=>"7b40ab6a-d522-4a86-b0de-dfb8081e4465", :controller=>"api/version1301/software", :action=>"post_event"}      # ./spec/controllers/api/version1301/software_controller_spec.rb:62:in `block (4 levels) in '

how handle route wildcard (event)?

(answering own question)

this turned out bit of 'rookie' mistake.

the wildcard (event) part of route still requires parameter. wasn't passing 'event' parameter, therefore route incomplete.

the following code works:

 describe "post_event"    "should respond 204"     params = {       attachment_id: @attachment.uid,       software_id: @license.id,       event: 'some/event'     }      post :post_event, params      response.code.should eq "204"   end end

/*event(.:format) means it's expecting parameter.

special note self , others:

if ever have routing errors in rails, verify you're passing parameters.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more