ismasan

/*
The MIT License (MIT)

Copyright (c) 2014 Ismael Celis

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is

gabehollombe

LabelOne LabelTwo
  - feature one (description one)

  - feature two (description two)

  - feature three with multiline desc following
    desc line 1
    desc line 2
    desc line 3

juliocesar

Testing front-end for a Sinatra app with RSpec and Capybara

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.

Gemfile

mwotton

require 'rspec'

class Bar
  def baz
    puts "baz called"
  end
end

class Foo
  def initialize

mrdoob

/**
 * Provides requestAnimationFrame in a cross browser way.
 * @author paulirish / http://paulirish.com/
 */

if ( !window.requestAnimationFrame ) {

	window.requestAnimationFrame = ( function() {

		return window.webkitRequestAnimationFrame ||

scottharvey

# Output information
watch('config/routes.rb') { system("clear; rake routes")}

# Run migrations
# watch('^db/migrate/(.*)\.rb') { |m| check_migration(m[1]) }

# # Run SASS
# watch('^app/stylesheets/(.*\.sass)') { |m| check_sass(m[1]) }

# # Run specific tests

scottharvey

tell application "Firefox"
	activate
end tell

tell application "System Events"
	tell process "Firefox"
		keystroke "r" using {command down}
	end tell
end tell

scottharvey

tell application "Terminal"
	activate
end tell

tell application "TextMate"
	activate
end tell

ryanb

Railties 3.1 RC4

• The new rake task assets:clean removes precompiled assets. [fxn]

• Application and plugin generation run bundle install unless --skip-gemfile or --skip-bundle. [fxn]

• Fixed database tasks for jdbc* adapters #jruby [Rashmi Yadav]

• Template generation for jdbcpostgresql #jruby [Vishnu Atrai]

dfurber

# These are my notes from the PragProg book on CoffeeScript of things that either 
# aren't in the main CS language reference or I didn't pick them up there. I wrote 
# them down before I forgot, and put it here for others but mainly as a reference for 
# myself.

# assign arguments in constructor to properties of the same name:
class Thingie
    constructor: (@name, @url) ->

# is the same as: