Rails テストに関する便利だけど見過ごされがちな 2 つの rake タスク - passingloopの日記
Rails テストで便利であるにもかかわらず知名度の低い、かわいそうな 2 つのタスク: rake test:recent タスク rake test:uncommitted タスク を紹介します。この記事は執筆時点の Rails 3.1.0.rc5 を対象としています。 Rails 謹製のテストタスク: rake test:* RSpec 使っていますか? もはや「デファクトスタンダードとなりつつある *1」 RSpec ですが、残念なことに私は使っていません。でも。そんな Test::Unit 遣いのために、Rails は便利な rake タスクを用意しています。たとえば、 rake test rake test:units rake test:functionals rake test:integration の各タスクは RailsによるアジャイルWebアプリケーション開発 第3版
FIXME, TODO and OPTIMIZE code comments
Random Ruby and Rails tips. This blog is dedicated to deliver short, interesting and practical tidbits of the Ruby language and Ruby on Rails framework. Read more... Your submissions are more than welcome! You can add some special notes to your source code comments in Rails to remind you later of stuff you need to do: class Article < ActiveRecord::Base # TODO add named_scopes # FIXME method A is b
“On Rake” by John Barnette
I’ve been reading a lot of Rakefiles lately, and it’s obvious that the folks writing them think of Rake as An Engine For Encapsulating Tasks. That’s fine, but it’s only part of what Rake can do. I Do Declare Rake is all about resolving dependencies. It’s about being declarative, not imperative. Especially when dealing with files and directories, this can make a huge difference. Here’s an example o
Ryan's Scraps: Using Command Line Parameters w/ Rake and Capistrano
Almost every project I work on requires a small set of both custom rake tasks and capistrano recipes. Since my models are as fat as they can be, these tasks and recipes are usually quite slim and really only involve delegation to the appropriate model method. Ok, so apparently Ryan thinks he’s great because he religiously believes in fat models – woohoo – that’s last year’s news. What I really wan
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Sake Bomb! — err.the_blog
