Sebastiaan Pouyet srpouyet

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

YARD CHEATSHEET http://yardoc.org

May 2020 - updated fork: https://gist.github.com/phansch/db18a595d2f5f1ef16646af72fe1fb0e

cribbed from http://pastebin.com/xgzeAmBn

Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.

Modules

Exposing an API

APIs are becoming an essential feature of modern web applications. Rails does a good job of helping your application provide an API using the same MVC structure you're accustomed to.

In the Controller

Let's work with the following example controller:

class ArticlesController &lt; ApplicationController

Sublime Text 2 – Useful Shortcuts (Mac OS X)

General

⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt

	# Just wanted to clarify my points at the meetup last night.
	#
	# There were two different issues intertwined:
	# (1) Whether to use extend or "include as extend"
	# (2) When using "include as extend", what is the simplest way to achieve the goal?
	#
	# My personal opinion is that the answer to (1) is "extend", not "include as extend", but that
	# is just my personal opinion. My answer to (2) is a more empirical question.

	# Using the "extend" approach. Again, I personally prefer the simplicity of this approach, but

	require 'faraday'
	require 'forwardable'

	module Soup
	class Agent
	extend Forwardable

	def initialize(domain = 'https://www.soup.io/')
	@agent \|\|= faraday(domain)
	end

	# CTags based autocompletion plugin for Sublime Text 2
	# You can add the file to the User Package in ~/Library/Application Support/Sublime Text 2/Packages and restart Sublime Text 2.
	# generate the .tags file in your project root with "ctags -R -f .tags"

	import sublime, sublime_plugin, os

	class AutocompleteAll(sublime_plugin.EventListener):

	def on_query_completions(self, view, prefix, locations):
	tags_path = view.window().folders()[0]+"/.tags"

	ENV["RAILS_ENV"] = "test"
	require File.expand_path('../../config/environment', __FILE__)

	require 'rubygems'
	gem 'minitest'
	require 'minitest/autorun'
	require 'action_controller/test_case'

	require 'miniskirt'
	require 'capybara/rails'

	ENV["RAILS_ENV"] = "test"
	require File.expand_path('../../config/environment', __FILE__)
	require 'rails/test_help'
	require 'minitest/autorun'
	require 'minitest/pride'
	require 'capybara/rails'


	class MiniTest::Spec
	include ActiveSupport::Testing::SetupAndTeardown

	module ApplicationHelper
	def content_for_or_pjax(name, &block)
	request.headers['X-PJAX'] ? capture(&block) : content_for(name, &block)
	end
	end