Luigi Ray-Montañez luigi

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

Nice speaker lineup for @BritRuby. Except for the 100% white guys part. I don't think adding diversity at the end works. You have to start with it as one of your goals. Who wants to be the token female? Not meaning to single out @BritRuby, just saying I'm disappointed. I know it's a systemic/cultural problem.

By what metric is @BritRuby "one of Europe’s… most diverse Ruby conferences"? Every speaker is a white man.

To an event organiser like myself @BritRuby's line [i.e. "we tried to reach out to non-white dudes but that didn't work"] is 100% bull... that line is getting stale. If you couldn't reach the speakers you haven't made the effort.

@BritRuby Are you saying minority speakers can't get in on merit? Plenty of confs have great speaker lineups that are not 100% white guys.

@BritRuby The comment is not unfair. Else why do you think selecting based on merit results in 100% white guys speaking?

	#!/usr/bin/env ruby

	# A simply utility to show character counts for each line of input and
	# highlight lines longer than 80 characters.
	#
	# Written as an example for http://jstorimer.com/2011/12/12/writing-ruby-scripts-that-respect-pipelines.html
	#
	# Examples:
	#
	# $ hilong Gemfile

	class PostsController < ActionController::Base
	def create
	Post.create(post_params)
	end

	def update
	Post.find(params[:id]).update_attributes!(post_params)
	end

	private

	source "https://rubygems.org"

	gem 'sprockets'
	gem 'sprockets-sass'
	gem 'sass'
	gem 'compass'
	gem 'bootstrap-sass'
	gem 'handlebars_assets'
	gem 'coffee-script'

	#!/usr/bin/env sh

	##
	# This is script with usefull tips taken from:
	# https://github.com/mathiasbynens/dotfiles/blob/master/.osx
	#
	# install it:
	# curl -sL https://raw.github.com/gist/2108403/hack.sh \| sh
	#

	1. USE OF EXTERNAL OPEN SOURCE SOFTWARE

	a) "Open Source Software" (OSS) is software that allows its recipients to modify and redistribute the source code; as such, "open source" is a copyright and distribution framework and makes no implications regarding technical support or indemnification. In almost all cases, OSS meets the definition of "commercial computer software" and shall be given appropriate statutory preference in accordance with 41 USC 264B (reference (b)) (see also FAR 2.101(b), 12_1.html 12.000, 12.101 (reference (c))).

	b) Executive agencies, including CFPB, are required to conduct market research when preparing for the procurement of products or services by 41 USC Sec. 253a (reference (e)) (see also FAR 10.001. Market research for software should include OSS.
	a. There are several positive aspects of OSS that should compel CFPB to seek out OSS when conducting market research on software for Bureau-wide use:
	i. Publicly available source code enables continuous and broad peer review that

	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"

	#!/usr/bin/env ruby

	require 'benchmark'

	REGEXPS = [
	/^no such file to load -- (.+)$/i,
	/^Missing \w+ (?:file\s*)?([^\s]+.rb)$/i,
	/^Missing API definition file in (.+)$/i,
	/^cannot load such file -- (.+)$/i,
	]