The step definitions below allow you to write this in both Webrat and Capybara:

When I follow "Download as PDF"
Then I should get a response with content-type "application/pdf"

Capybara

Then /^I should get a response with content-type "([^"]*)"$/ do |content_type|
  page.response_headers['Content-Type'].should == content_type
end

Webrat

Then /^I should get a response with content-type "([^"]*)"$/ do |content_type|
  response.content_type.should == content_type
end

Unfortunatly this do...

If a controller action responds to other formats than HTML (XML, PDF, Excel, JSON, ...), you can reach that code in a controller spec like this:

describe UsersController do
  describe '#index' do
    it 'should be able to send an excel file' do
       # stubs and expectations go here
       get :index, :format => 'xls'
    end
  end
end

Remember that both the :format parameter and the HTTP_ACCEPT header can m...

We use RTeX for PDF exports.
While converting LaTeX to PDF, RTeX opens a temporary file which has problematic permissions: Both group and world can read those files.

Although the temp files should go away they sometimes live longer than one would expect.
We patched RTeX to fix this (and have more secure permissions). Place the code below into config/initializers/rtex.rb

This is an awesome gadget in your toolbox, even if your test coverage is great.

• gem install ruby-debug (Ruby 1.8) or gem install debugger (Ruby 1.9)
• Start your server with script/server --debugger
• Set a breakpoint by invoking debugger anywhere in your code
• Open your application in the browser and run the code path that crosses the breakpoint
• Once you reach the breakpoint, the page loading will seem to "hang".
• Switch to the shell you started the server with. That shell will be running an irb session where you can step thr...

The following counts all the lines in all *.rb files in the app directory. Run several of these commands to get a rough estimate of the LOC.

find app -name *.rb -exec wc {} \; | awk '{a+=$1;print a}' | tail -1

This may be awkward to set up, but will work once you're done.

Fun facts:

• In case of a connection loss the slave will try to reconnect to the master server and resume replication for the next 24 hours
• If you want to use your slave as a "real" MySQL server, you basically need to switch off replication (STOP SLAVE; RESET SLAVE; and reset your my.cnf) and restart the MySQL daemon.

Master server configuration

• Create replication user
  : In the MySQL shell:

    CREATE USER 'replicator'@'%' IDENTI...