rob aldred » ruby

generate list of files for gem spec

Rob — Thu, 15 Apr 2010 13:50:31 +0000

Gemspec files require the list of files to include in the gem build, here’s simple command you can run to add all files descending from the current directory, it ignores the .git directory and sorts the list for you.

1	find . -type file \| grep -v .git/ \| sort

You just to add the ruby array syntax.
replace ./ with ”
replace \n with “,\n

Adding additional configuration args to selenium rc using cucumber and webrat

Rob — Thu, 25 Feb 2010 14:30:50 +0000

I use cucumber, webrat and selenium RC a lot day to day, all are great pieces of kit, which make my life so much easier, but I’m always trying to find ways to make these ever easier.
Selenium RC has alot of options which are settable when booting the selenium-server java application.
Many of these options are not available when using selenium with cucumber and webrat.

I have raised an issue for webrat and produced a patch that enables you to pass additional arguments during the setup of your webrat instance, these are then passed on to the Selenium RC startup command.

Until this is prioritised and added to the webrat core, I have an on-the-fly solution that enables the additional args, the following code should be added to your `env.rb`

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

module Webrat
class Configuration
attr_accessor :selenium_additional_args
end
end

module AdditionalArgs
def self.included(base)
base.alias_method_chain :start, :additional_args
end

def start_with_additional_args
remote_control.additional_args = Webrat.configuration.selenium_additional_args
start_without_additional_args
end
end

Webrat.configure do |config|
...
config.selenium_additional_args = ["-firefoxProfileTemplate '../../Library/Application Support/Firefox/Profiles/selenium'", "-singleWindow"]
...
end

Webrat::Selenium::SeleniumRCServer.send(:include, AdditionalArgs)

Testing ActionMailer models with Rspec

Rob — Mon, 14 Dec 2009 11:41:05 +0000

You might think testing ActionMailer sounds like a challenge, actually it’s just as easy as testing other classes, you just have to know the methods to use to change the state/content of the deliveries.

Here we have a simple example of how you might test a mailer for your order receipt

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

require File.dirname(__FILE__) + '/../spec_helper'

describe OrderMailer do

describe "receipt" do

before(:each) do
@order = mock_model(Order)
@order.customer = mock_model(Customer)
end

it "should render successfully" do
lambda { OrderMailer.create_receipt(@order) }.should_not raise_error
end

describe "rendered without error" do

before(:each) do
@mailer = OrderMailer.create_receipt(@order)
end

it "should have an order number" do
@mailer.body.should have_tag('.order_number', :text => @order.id)
end

it "should have order details" do
@mailer.body.should have_tag(".order_details")
end

it "should have a billing address" do
@mailer.body.should have_tag(".billing.address")
end

it "should have a delivery address" do
@mailer.body.should have_tag(".delivery.address")
end

it "should have customer contact details" do
@mailer.body.should have_tag("#contact_details") do
with_tag('.landline', :text => @order.customer.landline)
with_tag('.mobile', :text => @order.customer.mobile)
with_tag('.email', :text => @order.customer.email)
end
end

it "should have a list of items" do
@mailer.body.should have_tag(".line_items")
end

it "should have totals" do
@mailer.body.should have_tag(".totals") do
with_tag('.sub_total', :text => format_price(@order.sub_total))
with_tag('.vat', :text => format_price(@order.vat))
with_tag('.postage', :text => format_price(@order.postage))
with_tag('.total', :text => format_price(@order.total))
end
end

it "should deliver successfully" do
lambda { OrderMailer.deliver(@mailer) }.should_not raise_error
end

describe "and delivered" do

it "should be added to the delivery queue" do
lambda { OrderMailer.deliver(@mailer) }.should change(ActionMailer::Base.deliveries,:size).by(1)
end

end

end

end

end

rendering the following output:

ActionMailer test output from textmate rspec bundle

Cucumber pretty html formatter for textmate

Rob — Wed, 26 Aug 2009 11:23:48 +0000

I’ve been using cucumber a lot recently along with the textmate bundle for it.
The HTML output cucumber creates is fine, but not all that pretty.

I’ve created a new formatter for cucumber to generate HTML enhanced with some javascript.
My inspiration came from the textmate bundle for rspec.

You can grap it off my github.
Here’s some screenshots:

UPDATE: I replaced the original html formatter in cucumber; as of 19th November my fork has been merged into Aslak’s cucumber/master upgrade to the cucumber 0.4.5 release.
View the commit history

Custom log files for your ruby on rails applications

Rob — Wed, 14 Jan 2009 15:38:47 +0000

Sometimes logging is required but putting the messages in the Rails log isn’t the answer.For example you need to see the progress of customers through your order placement cycle, you ideally need this seperate to any other in a custom log file?

There is a solution and it’s easy… To create an order progress log, simply create a new instance of Logger and pass it a File instance for your own logfile.
Create a new model which inherits from Logger

class OrderProgressLogger < Logger
  def format_message(severity, timestamp, progname, msg)
  "#{timestamp.to_formatted_s(:db)} #{severity} #{msg}\n"
  end
end

Create initializer called logs.rb in RAILS_ROOT/config/initializers with the following content:

order_progress_logfile = File.open("#{RAILS_ROOT}/log/order_progress.log", 'a')
order_progress_logfile.sync = true
ORDER_PROGRESS_LOG = OrderProcessLogger.new(order_progress_logfile)

After a restart of your mongrel or passenger ORDER_PROGRESS_LOG will be available through out your application.
You log to it just as you would DEFAULT_RAILS_LOGGER like so…

ORDER_PROGRESS_LOG.debug "Starting order placement method"
ORDER_PROGRESS_LOG.error "Could not create order record"