softcraft-development

# Goal: Allow addition of instances to a collection in a factory-built object
# when those instances require references to the parent.
# Typically occurs in Rails when one model has_many instances of another

# See more at:
# http://stackoverflow.com/questions/2937326/populating-an-association-with-children-in-factory-girl

class Factory
  def has_many(collection)
    # after_build is where you add instances to the factory-built collection. 

netzpirat

Continuous CoffeeScript testing with Guard and Jasmine

This Gist shows how to set up a Rails project to practice BDD with CoffeeScript, Guard and Jasmine. You can see this setup in action on Vimeo

• Install Gems with Bundler with bundle install
• Define your guards with mate Guardfile
• Initialize Jasmine with bundle exec jasmine init
• Configure Jasmine with mate spec/support/yasmine.ym
• Start Guard with bundle exec guard

hosh

#http://eggsonbread.com/2010/03/28/my-rspec-best-practices-and-tips/
describe User do
  subject { user }
  let(:user) { User.new }

  context "when name empty" do
    it { should_not be_valid }
    specify { user.save.should be_false }
  end

mikegehard

Continuous CoffeeScript testing with Guard and Jasmine

This Gist shows how to set up a Rails project to practice BDD with CoffeeScript, Guard and Jasmine. You can see this setup in action on Vimeo

• Install Gems with Bundler with bundle install
• Define your guards with mate Guardfile
• Initialize Jasmine with bundle exec jasmine init
• Configure Jasmine with mate spec/support/yasmine.ym
• Start Guard with bundle exec guard

dhh

# autoload concerns
module YourApp
  class Application < Rails::Application
    config.autoload_paths += %W(
      #{config.root}/app/controllers/concerns
      #{config.root}/app/models/concerns
    )
  end
end

ramontayag

Intro

Problem: I learned how to run RSpec to test classes and modules in my gem. But, if I wanted to test my gem as if it were already included in a Rails app, I couldn't find much info about it online.

I usually do unit tests with RSpec, and I test the whole stack with Cucumber. So here we will just setup Cucumber to run the Rails app that you embed in your gem.

Before we begin:

• This tutorial is for people who already know how to make gems, and who have used RSpec and Cucumber before in a Rails app.
• MyGem and my_gem below refer to the name of the gem we are creating. Replace this with your own name.

semipermeable

# db/migrate/20110714024435_split_author.rb
class SplitAuthor < ActiveRecord::Migration
  def self.up
    Post.where(:author=>nil).each do |p|
      author = Author.create!(:name => p.author_name,
                              :account_id => p.account_id)
      p.author = author
      p.save!
    end
  end

bquorning

# Don't need passwords in test DB to be secure, but we would like 'em to be
# fast -- and the stretches mechanism is intended to make passwords
# computationally expensive.
module Devise
  module Models
    module DatabaseAuthenticatable

      def valid_password?(password)
        return false if encrypted_password.blank?

passcod

# Excess (v.FINAL)
# Félix Saparelli 2011-13
# Public Domain (CC0)

xs() { echo "Excess is dead. See https://github.com/passcod/bin"; }
xs-update() { xs; }

moa3

# config/initializers/active_admin_mongoid_patch.rb

require "active_admin"
require "active_admin/resource_controller"
require 'ostruct'

module ActiveAdmin
  class Namespace
    # Disable comments
    def comments?