| PADRINO_ENV = 'test' unless defined?(PADRINO_ENV) | |
| require 'rubygems' | |
| require 'spork' | |
| Spork.prefork do | |
| # Loading more in this block will cause your tests to run faster. However, | |
| # if you change any configuration or code from libraries loaded here, you'll | |
| # need to restart spork for it take effect. | |
| def tip(msg); puts; puts msg; puts "-"*100; end | |
| # | |
| # 30 Ruby 1.9 Tips, Tricks & Features: | |
| # http://www.igvita.com/2011/02/03/new-ruby-19-features-tips-tricks/ | |
| # | |
| tip "Upgrading to Ruby 1.9 is simple: rvm install 1.9.2 && rvm --default 1.9.2" | |
| tip "Ruby 1.9 supports named captures in regular expressions!" |
| # Patch to support customized request headers in your Capybara tests | |
| # when you're using the RackTest driver, based on an Aslak Hellesøy's gist: | |
| # https://gist.github.com/358664 | |
| # | |
| # Please note that some drivers don't allow access to headers, see: | |
| # https://github.com/jnicklas/capybara/issuesearch?state=closed&q=header#issue/17 | |
| class Capybara::Driver::RackTest < Capybara::Driver::Base | |
| def env |
In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax in sass, if you prefer it, it has no functional differences from the SCSS syntax.
For Less, I'm using the JavaScript version because this is what they suggest on the website. The ruby version may be different.
I've used Cucumber quite a bit on my last job. It's an excellent tool, and I believe readable tests are the way to the future. But I could never get around to write effective scenarios, or maintain the boatload of text that the suite becomes once you get to a point where you have decent coverage. On top of that, it didn't seem to take much for the suite to become really slow as tests were added.
A while ago I've seen a gist by Lachie Cox where he shows how to use RSpec and Capybara to do front-end tests. That sounded perfect for me. I love RSpec, I can write my own matchers when I need them with little code, and it reads damn nicely.
So for my Rails Rumble 2010 project, as usual, I rolled a Sinatra app and figured I should give the idea a shot. Below are my findings.
With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)
Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
Processing by HomeController#index as HTML
User Load (0.2ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
CACHE (0.0ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
Rendered layouts/_nav.html.erb (363.4ms)
| #!/bin/sh | |
| # Fetch and install the latest Chromium mac nightly build, but only | |
| # if it's different from the currently installed version. An existing | |
| # Chromium.app is backed up to .Chromium.app in the same directory. | |
| # | |
| # Install with: | |
| # $ curl -L http://bit.ly/night-chrome > ~/bin/nightly-chromium | |
| # $ chmod +x ~/bin/nightly-chromium | |
| # | |
| # To upgrade to latest chromium version: |
| require 'rubygems' | |
| require 'eventmachine' | |
| require 'em-websocket' | |
| require 'json' | |
| class Connection | |
| attr_accessor :socket, :user_id | |
| def initialize(socket, user_id) | |
| @socket = socket |
| # checkout: http://github.com/igrigorik/async-rails/ | |
| From bb2a78858cffa7c6937642986e9aca1a4f862c0d Mon Sep 17 00:00:00 2001 | |
| From: Ilya Grigorik <[email protected]> | |
| Date: Thu, 10 Jun 2010 00:46:48 -0400 | |
| Subject: [PATCH] async rails3 | |
| --- | |
| Gemfile | 6 ++++++ | |
| app/controllers/widgets_controller.rb | 6 ++++++ |
| =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') |
