zhengjia

=Navigating=
    visit('/projects')
    visit(post_comments_path(post))

=Clicking links and buttons=
    click_link('id-of-link')
    click_link('Link Text')
    click_button('Save')
    click('Link Text') # Click either a link or a button
    click('Button Value')

tsnow

We needed a better example for http://stackoverflow.com/questions/6267059/make-all-actionviewer-helper-methods-available-in-a-module/6271730#6271730

Other Resources on using helpers outside of ActionView:

http://drawohara.com/post/24582894/rails-un-suckass-ing-actionview-helpers-in-the-name

The other approach to this task is to use helpers for just the view oriented portions, and Presenters which are tied to them heavily. http://gilesbowkett.blogspot.com/2007/10/my-version-of-rails-presenters.html http://blog.new-bamboo.co.uk/2007/8/31/presenters-conductors-on-rails

jcasimir

Sessions and Conversations

HTTP is a stateless protocol. Sessions allow us to chain multiple requests together into a conversation between client and server.

Sessions should be an option of last resort. If there's no where else that the data can possibly go to achieve the desired functionality, only then should it be stored in the session. Sessions can be vulnerable to security threats from third parties, malicious users, and can cause scaling problems.

That doesn't mean we can't use sessions, but we should only use them where necessary.

Adding, Accessing, and Removing Data

thermistor

namespace :assets do

  desc "Check that all assets have valid encoding"
  task  :check => :environment do

    paths = ["app/assets", "lib/assets", "vendor/assets"]
    extensions = ["js", "coffee", "css", "scss"]

    paths.each do |path|
      dir_path = Rails.root + path

larskanis

require 'active_record'

ActiveRecord::Base.configurations['my_connect'] = {:adapter=>'sqlite3', :database=>'fixture_database.sqlite3'}

class Car < ActiveRecord::Base
  establish_connection 'my_connect'
  has_many :tyres
end

class Tyre < ActiveRecord::Base

psahni

require 'spec_helper'

feature "Editing tickets" do
  let!(:project) { Factory(:project) }
  let!(:ticket) { Factory(:ticket, :project => project) }

  before do
    visit '/'
    click_link project.name
    click_link ticket.title

oma

development: &defaults
  # Configure available database sessions. (required)
  sessions:
    # Defines the default session. (required)
    default: &default_session
      # Defines the name of the default database that Mongoid can connect to.
      # (required).
      database: delight_development
      # Provides the hosts the default session can connect to. Must be an array
      # of host:port pairs. (required)

roberto

<% flash.each do |type, message| %>
  <div class="alert <%= bootstrap_class_for(type) %> fade in">
    <button class="close" data-dismiss="alert">×</button>
    <%= message %>
  </div>
<% end %>

psahni

namespace :deploy do
  desc "Hot-reload God configuration for the Resque worker"
  task :reload_god_config do
    sudo "god stop resque"
    sudo "god load #{File.join(deploy_to, 'current', 'config', 'resque-' + rails_env + '.god')}"
    sudo "god start resque"
  end
end

# append to the bottom:

nhance

Model.new.foo