Disqus - Latest Comments for court3nay

Re: I am rice

court3nay — Sun, 11 Nov 2007 17:17:56 -0000

you don't need this since 1.1.1, just hit space twice.

Re: New 24″ iMac

court3nay — Tue, 20 May 2008 01:32:10 -0000

The 24" imac is unique in that it has a S-IPS panel in it (better viewing angle, 24-bit color). The S-IPS is basically the best panel available in consumer devices and is not present in the smaller imacs. They tend not to advertise which panel is in a display, but you can infer it from the published viewing angle specs.

Re: RESTful Programming and CSRF

court3nay — Sat, 29 Mar 2008 22:27:16 -0000

It's a dirty little secret of rails apps that many of them are susceptible to csrf attacks. However, if you designed your rails app correctly (i.e. GET actions only show data, to delete you have to post with DELETE) it makes it a little more difficult, because you need a POST to change any data.

There was a twitter 'virus' a few months that we discovered and destroyed that essentially created a form which created a tweet and POSTed the form automatically with javascript.

My colleague Rick Olson wrote CSRF_killer plugin which automatically puts some hidden form variables into all of your forms, and effectively squashes any such attacks.

Re: New 24″ iMac

court3nay — Tue, 20 May 2008 01:32:10 -0000

Re: Rails don't know testing

court3nay — Sun, 18 Mar 2007 17:19:00 -0000

Wow. First of all, you don’t need Mysql to run tests. You do (mostly) need a database, since you really do want to test your whole stack.

However, you don’t actually need a database to test your controller.

In fact, the way you have it set up above, you can’t change the implementation of the ‘search’ call without messing about in your controller tests, even though it’s a database call. You essentially are testing the framework, no your code.

You could wrap your ‘search’ call in a class method, so that:

def User.search(q)
  find(:all, :conditions => ['name like ?', "#{q}"])
end

Now, your controller test looks like

User.expects(:search).with(q).returns users

And the controller looks like

def search
  @users = User.search(params[:q])
end

And you can change the ordering, add includes, or even switch in Ferret, and you wouldn’t have to change the controller test. Think about it—those db calls (“LIKE %“) should be hidden away in the model, and they should be tested in your model’s tests.

Re: Introducing the Shoulda Testing Plugin

court3nay — Fri, 06 Apr 2007 15:20:00 -0000

Heh. Haven’t you heard of test/spec?

http://chneukirchen.org/blog/archive/2006/10/announcing-test-spec-0-2-a-bdd-interface-for-test-unit.html

http://poocs.net/2007/4/3/test-spec-on-rails-and-assert_difference

http://weblog.techno-weenie.net/2006/11/24/test-spec-kicks-simply_bdds-ass

Re: cruise_control.rb campfire plugin

court3nay — Sat, 21 Apr 2007 01:24:00 -0000

woot, my li’l marshmallow really gets around :) good to see he’s still useful to people.

Re: true or false

court3nay — Wed, 25 Apr 2007 14:53:00 -0000

You really really need to look into the State Machine plugin.

It’s a bit of a learning curve, but it will make your code much more powerful and foolproof. You can guard against changing states, provide callbacks on state changes, as well as only allow a ceratain pathway from/to each state.

http://rubyi.st/2006/1/21/acts-as-state-machine

http://www-128.ibm.com/developerworks/java/library/j-cb03137/index.html