ryanb

These are some of my (Ryan Bates) favorite gems to use for various tasks:

• JavaScript: jQuery with jquery-rails
• Pagination: Kaminari
• Testing: RSpec, Cucumber and Capybara
• Factories: Factory Girl
• Authentication: Nifty Generators and Omniauth
• Authorization: CanCan
• File Attachments: Carrierwave
• HTML/XML Parsing: Nokogiri

ryanb

<!-- layout file -->
<% if current_user %>
  Welcome <%= current_user.username %>. Not you? <%= link_to "Log out", logout_path %>
<% else %>
  <%= link_to "Sign up", signup_path %> or <%= link_to "log in", login_path %>.
<% end %>

tdreyno

gem 'rspec', "~> 2.1.0"
require 'rspec'
require 'lebowski/rspec'

include Lebowski::Foundation
include Lebowski::Foundation::Views
include Lebowski::Foundation::Panes
include Lebowski::SCUI::Views

Before do

danielvlopes

require "spec/acceptance/acceptance_helper"

feature "Login", %q{
  In order to access my account
  As an user
  I want to be able to log in
} do

  let :user do
    Factory :user

ianwhite

(posted at http://groups.google.com/group/cukes/browse_thread/thread/4e01cc6e1a7071d4)

Hi Guys, 

I'm the author of pickle, and despite this I broadly agree with Jonas' point of view. 
The power of capybara is best realised when you do away with web_steps.rb, and start writing your own steps using capybara's dsl.

In my opinion, pickle is likewise.  pickle_steps.rb is a general set of steps to both introduce the dev to the dsl, and enable rapid cuke writing in the early stages of a project. 

I agree with Nick - the main point of pickle is to provide a general way of storing models for the lifetime of a scenario, and also to provide a general way of referring to them, so that you don't have to have step defs littered with variable names 

triskweline

# Copy this to features/support/ssl_fix.rb to make Capybara work with sites that switch between HTTP and HTTPS

module Capybara::Driver::RackTest::SslFix

  [:get, :post, :put, :delete].each do |method|
    define_method method do |*args|
      args[0] = path_to_ssl_aware_url(args[0])
      super(*args)
    end
  end

kneath

GitHub Javascript Strategy

Unless otherwise necessary (such as mobile development), the GitHub javascript codebase is based off jQuery. You can safely assume it will be included on every page.

File naming

• All jquery plugins should be prefixed with jquery, such as jquery.facebox
• All github-specific jquery plugins should be prefixed with jquery.github. Like jquery.github.repo_list.js
• All page-specific files (that only run on ONE page) should be prefixed with page. page.billing.js

dburger

namespace :minifier do

  def minify(files)
    files.each do |file|
      cmd = "java -jar lib/yuicompressor-2.3.1.jar #{file} -o #{file}"
      puts cmd
      ret = system(cmd)
      raise "Minification failed for #{file}" if !ret
    end
  end